https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2022-06-24T08:20:08ZSaxonica Developer CommunitySaxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211442022-06-24T08:20:08ZNorm Tovey-Walsh
<ul></ul><p>Hi,</p>
<p>Thanks for the observation. When the “data” jar was created, I tried to<br>
work out how classifiers were represented in filenames. I came to the<br>
conclusion that the format was “name-version-classifier”. If I’m<br>
mistaken, I’ll switch to “name-classifier-version” for the next release.</p>
<p>Be seeing you,<br>
norm</p>
<p>--<br>
Norman Tovey-Walsh <a href="mailto:ndw@nwalsh.com" class="email">ndw@nwalsh.com</a><br>
<a href="https://nwalsh.com/" class="external">https://nwalsh.com/</a></p>
<blockquote>
<p>5% of the world's population consumes a third of its resources and<br>
makes nearly half its waste. That 5% is US.</p>
</blockquote> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211452022-06-24T08:34:59ZJohan Gheys
<ul></ul><p>For us, it is a jar file like any other that we load via a maven dependency. Therefore, we use the filename of the documentation internally. It would just be convenient if we didn't have to do the rename in the future.</p> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211462022-06-24T08:49:42ZNorm Tovey-Walsh
<ul></ul><p>Saxonica Developer Community <a href="mailto:notifications@plan.io" class="email">notifications@plan.io</a> writes:</p>
<blockquote>
<p>For us, it is a jar file like any other that we load via a maven<br>
dependency. Therefore, we use the filename of the documentation<br>
internally. It would just be convenient if we didn't have to do the<br>
rename in the future.</p>
</blockquote>
<p>Right. I’ll try to get that sorted out before the next release.</p>
<p>Be seeing you,<br>
norm</p>
<p>--<br>
Norman Tovey-Walsh <a href="mailto:ndw@nwalsh.com" class="email">ndw@nwalsh.com</a><br>
<a href="https://nwalsh.com/" class="external">https://nwalsh.com/</a></p>
<blockquote>
<p>Happiness is nothing more than good health and a bad memory.--Albert<br>
Schweitzer</p>
</blockquote> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211472022-06-24T08:56:56ZJohan Gheys
<ul></ul><p>Ok, perfect, thanks for the willingness</p> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211492022-06-24T09:11:17ZMichael Kaymike@saxonica.com
<ul><li><strong>Assignee</strong> set to <i>Norm Tovey-Walsh</i></li></ul> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211602022-06-27T11:27:49ZNorm Tovey-Walsh
<ul></ul><p>Either this is a case of conflicting expectations, or there's something else going on that I don't undertand. I went back to see if I could resolve why the name was not consistent with common practice. What I discovered is that I'm using this task:</p>
<pre><code>task dataJar(type: Jar, dependsOn: ["copyData"]) {
archiveBaseName = "${basename}-${resolverVersion}"
classifier = 'data'
from "${buildDir}/data"
manifest {
attributes "Built-By": "Norman Walsh"
attributes "Implementation-Vendor": "Norman Walsh"
attributes "Implementation-Title": "XML Resolver data"
attributes "Implementation-Version": resolverVersion
attributes "Automatic-Module-Name": "org.xmlresolver.xmlresolver_data"
}
}
</code></pre>
<p>Note that I'm not explicitly locating the classifier in the jar filename. When I lookup the <code>Jar</code> task in the Gradle documentation, I find:</p>
<blockquote>
<p>If the name has not been explicitly set, the pattern for the name is:</p>
<pre><code>[archiveBaseName]-[archiveAppendix]-[archiveVersion]-[archiveClassifier].[archiveExtension]
</code></pre>
</blockquote>
<p>That suggests to me that (at least in the Gradle community) the expectation is that the classifier comes after the version.</p>
<p>Do you recall where you found the "version comes last" convention?</p> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211612022-06-27T12:10:17ZJohan Gheys
<ul></ul><p>We load the jar file via a maven dependency and follow the maven convention of groupId, artifactId and version. The easiest way for us is to rename xmlresolver-4.2.0-data.jar to xmlresolverdata-4.2.0.jar as mentioned in the documentation. But if this causes problems on your side, you may as well change the documentation.</p> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211662022-06-28T13:34:56ZNorm Tovey-Walsh
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Documentation updated. Apologies for not seeing that more quickly!</p> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=211672022-06-28T16:48:10ZJohan Gheys
<ul></ul><p>No problem and thanks for the alignment.</p> Saxon - Support #5581: Name of the jar file xmlresolver-4.2.0-data.jar not aligned with documentationhttps://saxonica.plan.io/issues/5581?journal_id=224682023-01-13T19:46:35ZO'Neil Delprattoneil@saxonica.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>