[prev in list] [next in list] [prev in thread] [next in thread]
List: xalan-j-users
Subject: Re: Xalan 2.7.3 in maven
From: Jens_Annighöfer <jens () annighoefer ! net>
Date: 2023-04-12 18:32:13
Message-ID: 7a2e78cf-d8a9-e2d0-9d6b-5e4d9a56cb62 () annighoefer ! net
[Download RAW message or body]
We think, that xml-apis.jar is a snapshot, build from the sources
located here:
https://svn.apache.org/repos/asf/xerces/xml-commons/trunk/java/external/.
The version 1.4.02 can be found in
https://svn.apache.org/repos/asf/xerces/xml-commons/trunk/java/external/build.xml
Since the version 1.4.02 was never released we decided to ignore the
xml-apis.jar in the xalan distribution and to use the wellknown version
1.4.01.
Best regards, Jens
Am 12.04.2023 um 17:29 schrieb Gary Gregory:
> Another reason to use Maven ;-)
> (As opposed to Ivy which I am not a fan of)
>
> Gary
>
> On Wed, Apr 12, 2023, 10:58 Eric J. Schwarzenbach
> <eric.schwarzenbach@wrycan.com> wrote:
>
> Even setting the maven question aside for a moment, where does this
> xml-apis.jar even come from? As I noted, the manifest of the
> xml-apis.jar that comes with the xalan 2.7.3 download indicates a
> version of 1.4.02 (Implementation-Version). It also gives
> "Implementation-URL: http://xml.apache.org/commons/" But following
> that
> link to the xml commons project, I can find no download for
> 1.4.02, only
> 1.4.01. Xalan does not provide the source that that jar in it's
> source
> download as far as I can tell.
>
>
> On 4/11/23 01:29, Mukul Gandhi wrote:
> > Hi Eric,
> >
> > On Mon, Apr 10, 2023 at 10:40 PM Eric J. Schwarzenbach
> > <eric.schwarzenbach@wrycan.com> wrote:
> >
> >> This isn't about what is used to build Xalan, but about what
> Xalan's
> >> users use to build their projects and ensure they use Xalan
> with correct
> >> dependencies. Maven is what a large chunk of Java users use for
> >> dependency management, and they typically expect to be able to
> pull the
> >> dependency definitions from Maven central. Of course they can each
> >> individually set this up locally instead, but it is more ideal
> to have
> >> central source of correct information. Maven central serves
> that role
> >> and contains such definitions for previous versions of Xalan.
> >>
> >> Of course the Xalan devs do not necessarily have to be the ones
> >> submitting this to maven central, some Xalan user more familiar
> with
> >> maven, like Richard or myself, could probably step up and do this.
> >> However it would be helpful for a Xalan dev to chime in
> regarding the
> >> correct / necessary versions of dependencies. I posted a query for
> >> clarification about one such dependency version recently
> (xml-apis.jar)
> >> to this list but have not as yet seen a reply. Perhaps it will
> help to
> >> give more context, if you are not a maven user yourself.
> >>
> >> Typically when a Maven user sets up the maven dependency
> definitions for
> >> a new version of something, they will start with the previous
> versions
> >> definitions as a starting point. The definitions in maven
> central for
> >> Xalan 2.7.2, declares two (compile) dependencies: xercesImpl
> 2.9.1 and
> >> serializer 2.7.2. Note that such dependency declarations will
> cause a
> >> user's project build to pull in these dependencies
> automatically, so a
> >> projecting declaring xalan 2.7.2 will get xercesImpl 2.9.1
> >> automatically. Some users like myself, have project that also
> depend on
> >> xerces directly and realize that newer versions of xerces have
> come out
> >> and define their project to reference a newer version of xerces
> like
> >> 2.12.2.
> >>
> >> xercesImpl in turn has a maven definition that declares a
> dependency on
> >> xml-apis. xercesImpl 2.12.2 specifies xml-apis 1.4.01. The is
> the latest
> >> version of xml-apis appearing in Maven central (ignoring the
> versions
> >> 2.0.0 and 2.0.2 which are actually older than 1.4.01...I forget the
> >> story there.)
> >>
> >> To reiterate my earlier query, I notice that the jars included
> with the
> >> xalan 2.7.3 download include an xml-apis that seems to be version
> >> 1.4.02. Is it necessary or in some way desirable to use xalan
> 2.7.3 with
> >> that version of xml-apis rather than to let the xercesImpl
> dependency
> >> pull in xms-apis 1.4.01? If so, maybe we need to declare that
> as direct
> >> dependency of the xalan maven definition, and load that artifact to
> >> maven central also. But where does it come from? What project
> manages
> >> and produces this jar?
> >>
> >> Any advice here would be much appreciated by maven users,
> either for
> >> setting up their own local maven dependency definitions, or
> (preferably)
> >> for someone to submit a canonical definition to maven central.
> > XalanJ is a special Java library, within the Java language
> ecosystem.
> > XalanJ is part of JDK itself (as an implementation of, JAXP XSLT and
> > XPath APIs. Ref,
> > https://www.oracle.com/java/technologies/jaxp-introduction.html). I
> > think, its better if, XalanJ project distributes its jars as
> > standalone downloadables (as has been done, with XalanJ 2.7.3
> with its
> > Ant build), and let XalanJ users configure these jars within for e.g
> > Maven build environment however XalanJ users wish.
> >
> >
>
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>We think, that xml-apis.jar is a snapshot, build from the sources
located here: <a moz-do-not-send="true"
href="https://svn.apache.org/repos/asf/xerces/xml-commons/trunk/java/external/"
class="moz-txt-link-freetext">https://svn.apache.org/repos/asf/xerces/xml-commons/trunk/java/external/</a>.
The version 1.4.02 can be found in <a moz-do-not-send="true"
href="https://svn.apache.org/repos/asf/xerces/xml-commons/trunk/java/external/build.xml"
class="moz-txt-link-freetext">https://svn.apache.org/repos/asf/xerces/xml-commons/trunk/java/external/build.xml</a><br>
</p>
<div class="moz-cite-prefix">Since the version 1.4.02 was never
released we decided to ignore the xml-apis.jar in the xalan
distribution and to use the wellknown version 1.4.01.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Best regards, Jens<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 12.04.2023 um 17:29 schrieb Gary
Gregory:<br>
</div>
<blockquote type="cite"
cite="mid:CACZkXPzt+5NRq0nPa=-FzuV-R-CojY+We0rq49fsrRarxdq_qQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Another reason to use Maven ;-)
<div dir="auto">(As opposed to Ivy which I am not a fan of)</div>
<div dir="auto"><br>
</div>
<div dir="auto">Gary</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Apr 12, 2023, 10:58
Eric J. Schwarzenbach <<a
href="mailto:eric.schwarzenbach@wrycan.com"
moz-do-not-send="true" \
class="moz-txt-link-freetext">eric.schwarzenbach@wrycan.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Even setting
the maven question aside for a moment, where does this <br>
xml-apis.jar even come from? As I noted, the manifest of the <br>
xml-apis.jar that comes with the xalan 2.7.3 download
indicates a <br>
version of 1.4.02 (Implementation-Version). It also gives <br>
"Implementation-URL: <a href="http://xml.apache.org/commons/"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" \
class="moz-txt-link-freetext">http://xml.apache.org/commons/</a>" But following that \
<br> link to the xml commons project, I can find no download for
1.4.02, only <br>
1.4.01. Xalan does not provide the source that that jar in
it's source <br>
download as far as I can tell.<br>
<br>
<br>
On 4/11/23 01:29, Mukul Gandhi wrote:<br>
> Hi Eric,<br>
><br>
> On Mon, Apr 10, 2023 at 10:40 PM Eric J. Schwarzenbach<br>
> <<a href="mailto:eric.schwarzenbach@wrycan.com"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">eric.schwarzenbach@wrycan.com</a>>
wrote:<br>
><br>
>> This isn't about what is used to build Xalan, but
about what Xalan's<br>
>> users use to build their projects and ensure they use
Xalan with correct<br>
>> dependencies. Maven is what a large chunk of Java
users use for<br>
>> dependency management, and they typically expect to
be able to pull the<br>
>> dependency definitions from Maven central. Of course
they can each<br>
>> individually set this up locally instead, but it is
more ideal to have<br>
>> central source of correct information. Maven central
serves that role<br>
>> and contains such definitions for previous versions
of Xalan.<br>
>><br>
>> Of course the Xalan devs do not necessarily have to
be the ones<br>
>> submitting this to maven central, some Xalan user
more familiar with<br>
>> maven, like Richard or myself, could probably step up
and do this.<br>
>> However it would be helpful for a Xalan dev to chime
in regarding the<br>
>> correct / necessary versions of dependencies. I
posted a query for<br>
>> clarification about one such dependency version
recently (xml-apis.jar)<br>
>> to this list but have not as yet seen a reply.
Perhaps it will help to<br>
>> give more context, if you are not a maven user
yourself.<br>
>><br>
>> Typically when a Maven user sets up the maven
dependency definitions for<br>
>> a new version of something, they will start with the
previous versions<br>
>> definitions as a starting point. The definitions in
maven central for<br>
>> Xalan 2.7.2, declares two (compile) dependencies:
xercesImpl 2.9.1 and<br>
>> serializer 2.7.2. Note that such dependency
declarations will cause a<br>
>> user's project build to pull in these dependencies
automatically, so a<br>
>> projecting declaring xalan 2.7.2 will get xercesImpl
2.9.1<br>
>> automatically. Some users like myself, have project
that also depend on<br>
>> xerces directly and realize that newer versions of
xerces have come out<br>
>> and define their project to reference a newer version
of xerces like<br>
>> 2.12.2.<br>
>><br>
>> xercesImpl in turn has a maven definition that
declares a dependency on<br>
>> xml-apis. xercesImpl 2.12.2 specifies xml-apis
1.4.01. The is the latest<br>
>> version of xml-apis appearing in Maven central
(ignoring the versions<br>
>> 2.0.0 and 2.0.2 which are actually older than
1.4.01...I forget the<br>
>> story there.)<br>
>><br>
>> To reiterate my earlier query, I notice that the jars
included with the<br>
>> xalan 2.7.3 download include an xml-apis that seems
to be version<br>
>> 1.4.02. Is it necessary or in some way desirable to
use xalan 2.7.3 with<br>
>> that version of xml-apis rather than to let the
xercesImpl dependency<br>
>> pull in xms-apis 1.4.01? If so, maybe we need to
declare that as direct<br>
>> dependency of the xalan maven definition, and load
that artifact to<br>
>> maven central also. But where does it come from? What
project manages<br>
>> and produces this jar?<br>
>><br>
>> Any advice here would be much appreciated by maven
users, either for<br>
>> setting up their own local maven dependency
definitions, or (preferably)<br>
>> for someone to submit a canonical definition to maven
central.<br>
> XalanJ is a special Java library, within the Java
language ecosystem.<br>
> XalanJ is part of JDK itself (as an implementation of,
JAXP XSLT and<br>
> XPath APIs. Ref,<br>
> <a
href="https://www.oracle.com/java/technologies/jaxp-introduction.html"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" \
class="moz-txt-link-freetext">https://www.oracle.com/java/technologies/jaxp-introduction.html</a>).
I<br>
> think, its better if, XalanJ project distributes its jars
as<br>
> standalone downloadables (as has been done, with XalanJ
2.7.3 with its<br>
> Ant build), and let XalanJ users configure these jars
within for e.g<br>
> Maven build environment however XalanJ users wish.<br>
><br>
><br>
</blockquote>
</div>
</blockquote>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic