Remy Maucherat wrote:
>
> Well, it only needs JAXP 1.0. There are no JAXP 1.1 specific
> calls.
>
> Same : it requires only the Servlet API 2.2 (it can run on
> TC 3.2). I don't know if being built against the 2.3 API
> would make the build dependent on the 2.3 API, or if it
> still could be run on TC 3.2.

My main focus at the moment is to see if changes to dependencies will break
other projects.

By the way, I don't use the Sun JAXP implementation in the build - it is
only needed because the build.xml requires these jar files to copy.  What I
am actually using in Xerces.

The real goal of JAXP is to make parsers pluggable.  So you continue
building using JAXP 1.0, and I will build using Xerces.

> > < <work nested="build/classes"/>
> > < <work nested="build/client/classes"/>
> >
> > I need this to build the examples.
>
> Really ? I've added some more classpath information.

This is an unfortunate aspect of gump at the moment.  People tend to put a
lot of classpath information in their build.xml, and I know of no clean way
to determine which should be respected and which should be ignored.  So I
ignore them all ;-).  Then I add back in the necesary ones in the project
definition.

> > < <option project="jakarta-tomcat-4.1"/>
> > > <option project="jakarta-tomcat-4.0"/>
> >
> > Why?
>
> 4.1 is the temporarily dead dev branch.

I've been optimistic that this was only temporary for a while.

OK, I've temporarily removed it.

- Sam Ruby


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to