ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <jakarta-...@ehatchersolutions.com>
Subject Re: [IMPORTANT!] Fix Ant 1.5 Support for JAXP [Was: XMLCatalog.java -- patch breaks bootstrap.bat Yikes!]
Date Mon, 27 May 2002 12:22:33 GMT
I won't have time to get to this until much later tonight at the earliest,
but again could you submit patches that you want applied as a unit all
together in a single patch file?  It would be *most* helpful and expedite
them being applied.... unless someone wants to share a trick to applying
multiple patches like this in one shot.  I'm simply doing 'patch -p0 <
filename' which requires me to put these patch files in the proper directory
(which is why one patch from the root directory is best for me) and then
change into each directory to apply them manually.

Adding the xml-apis.jar to lib/optional fixed bootstrap for me, at least.

    Erik



----- Original Message -----
From: "Craeg K Strong" <cstrong@arielpartners.com>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Sent: Monday, May 27, 2002 1:00 AM
Subject: Re: [IMPORTANT!] Fix Ant 1.5 Support for JAXP [Was:
XMLCatalog.java -- patch breaks bootstrap.bat Yikes!]


> [PROPOSAL]
>
> What about this as an alternative:
>
> 1) replace xmlParserAPIs.jar with xml-apis.jar in lib/
> 2) put xalan.jar in lib/optional
> 3) apply the attached patches to bootstrap.bat, bootstrap.sh,
>     build.sh, build.bat, and build.xml
>
> xml-apis.jar seems to be a strict superset of xmlParserAPIs.jar
> That is, it is the same except that it includes the entire JAXP
> rather than xerces' chopped down version.
>
> The patches to bootstrap.{sh,bat} and build.{sh,bat} merely substitute
> xml-apis.jar for xmlParserAPIs.jar
>
> The patch to build.xml modifies the "trax.present" condition so that
> it accurately reports the presence of an _implementation_ of trax, rather
> than the _interface_ of the trax/JAXP API.
>
> Advantages:
>
> - xalan.jar is not required for bootstrapping
> - If you want to execute XsltTest, simply include xalan.jar in your path.
>    otherwise it is ommitted
>
> I tried this out on both Windows 2000 and Red Hat Linux 7.2 with
> Java 1.3.1_03 and it seemed to work fine (although some other testcases
> failed for me...?)
>
> Thoughts?
>
> --Craeg
>
> Conor MacNeill wrote:
> > costinm@covalent.net wrote:
> >
> >> On Mon, 27 May 2002, Conor MacNeill wrote:
> >>
> >> There is a section in all JCP specs that (aledgedly) require any
> >> implementation to pass a test suite, otherwise it can't be distributed.
> >> There are also requirements to distribute the full impl, not a subset.
> >> Of course, xerces is a clean-room implementation ( but as it was
> >> discussed, it is not clear if clean-room is ok - and some people who
> >> contributed on the impl. have read the spec ).
> >>
> >> Again, it all depends on how much you care about small prints and
> >> how you want to interpret it. Some believe that are issues with the
> >> parts of the licence that restrict clean-room impl of a spec. And I
doubt
> >> Sun will sue ASF for this.
> >> In any case, distributing Jaxp without Xalan can't be called a
> >>  'JAXP1.1 implementation', and can't pass the test suite ( since
> >> 1/2 tests are for XSLT ).
> >> For an official answer you should contact Sam Ruby, or someone who
> >> have access to the licensing list on ASF. All I can say is that
> >> distributing it without xalan makes me very uncomfortable.
> >
> >
> > OK thanks. IANAL either so the following is just my opinion :-)
> >
> > According to the current JCP requirements I'm not sure we could
> > distribute Ant with either Xerces or Xalan since I am not aware that
> > either pass their JCP test suite (there may be some exemptions
> > negotiated for Apache that I am unaware of). If the press releases were
> > any guide, this issue should be resolved but I don't think the final
> > resolution has happened yet.
> >
> > You know, if what you contend is true, Xerces itself could not be
> > distributed without Xalan :-)
> >
> > If we do decide to include Xalan we need to figure out which xml-apis
> > jar to include since Xerces and Xalan appear to use different versions
> > :-( Can anyone vouch for the suitability of using Xerces with Xalan's
> > xml-apis jar or do we have to take a leap of faith?
> >
> > Conor
> >
>


----------------------------------------------------------------------------
----


> --
> To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message