On 30 Oct 2004, David Crossley [EMAIL PROTECTED] wrote:
By the way, if any Ant committers want to help the
poor neglected XML Commons project, then come on over.
Oh, we asked for a release every now[1] and then. That's all I can
offer, given my ignorance about the code itself. 8-)
In a later
On Fri, 29 Oct 2004, Dion Gillard [EMAIL PROTECTED] wrote:
The xmlParserAPIs is from memory a rename of xml-apis from
xml-commons, provided by xerces in it's download, right?
Yes and no.
The version shipped by Xerces is far more advanced than the latest
released version (and even that has
Stefan Bodewig wrote:
Dion Gillard wrote:
The xmlParserAPIs is from memory a rename of xml-apis from
xml-commons, provided by xerces in it's download, right?
Yes and no.
The version shipped by Xerces is far more advanced than the latest
released version (and even that has been a
On 29 Oct 2004, David Crossley [EMAIL PROTECTED] wrote:
Stefan Bodewig wrote:
I understood that xml-commons was supposed to be the
official home.
So do I.
When we prepared the release of Ant 1.6.0 we realized that Xerces
wouldn't work with the 1.0beta2 release from xml-commons, so we were
Stefan Bodewig wrote:
David Crossley wrote:
Stefan Bodewig wrote:
I understood that xml-commons was supposed to be the
official home.
So do I.
When we prepared the release of Ant 1.6.0 we realized that Xerces
wouldn't work with the 1.0beta2 release from xml-commons, so we were
On 29 Oct 2004, David Crossley [EMAIL PROTECTED] wrote:
Stefan Bodewig wrote:
David Crossley wrote:
Stefan Bodewig wrote:
I understood that xml-commons was supposed to be the
official home.
So do I.
When we prepared the release of Ant 1.6.0 we realized that Xerces
wouldn't work
Stefan Bodewig wrote:
David Crossley wrote:
Stefan Bodewig wrote:
David Crossley wrote:
Stefan Bodewig wrote:
I understood that xml-commons was supposed to be the
official home.
So do I.
When we prepared the release of Ant 1.6.0 we realized that Xerces
wouldn't work
On Thu, 28 Oct 2004, Niclas Hedhman [EMAIL PROTECTED] wrote:
Feel free to try to get the name xmlParserAPIs to map against the
Maven artifactID of the same name.
I'm still not sure how to do that exactly, but if the project name is
enough, the alias project I've created in the xml-xerces2
On Thu, 28 Oct 2004 11:12:50 +0800, Niclas Hedhman [EMAIL PROTECTED] wrote:
On Thursday 28 October 2004 07:07, David Crossley wrote:
Is this the same xml-apis that are provided by
Apache XML Commons?
Class-wise, probably yes.
But Fulcrum uses the xmlParserAPIs Maven artifactId, and I
On 27 Oct 2004, [EMAIL PROTECTED] wrote:
Adding the xmlParserAPIs for some Maven projects in Fulcrum.
+ project name=xmlParserAPIspackage=jetty-5.0.RC4/
Isn't this the same jar that we created during the Xerces build? The
2.5 in the jar name in Jetty suggests Xerces-J 2.5 to me.
On Wednesday 27 October 2004 23:46, Stefan Bodewig wrote:
On 27 Oct 2004, [EMAIL PROTECTED] wrote:
Adding the xmlParserAPIs for some Maven projects in Fulcrum.
+ project name=xmlParserAPIspackage=jetty-5.0.RC4/
Isn't this the same jar that we created during the Xerces build? The
Niclas Hedhman wrote:
Stefan Bodewig wrote:
Niclas Hedman wrote:
Adding the xmlParserAPIs for some Maven projects in Fulcrum.
+ project name=xmlParserAPIspackage=jetty-5.0.RC4/
Isn't this the same jar that we created during the Xerces build? The
2.5 in the jar name in
12 matches
Mail list logo
