You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Antoine Lévy-Lambert <an...@antbuild.com> on 2004/01/19 15:08:38 UTC
jaxen does not build in some gump instances
Hi,
I am interested in seeing jaxen build in gump.
On some gump instances, the build of jaxen is failing (see footnotes).
I am an ant developer, and I need jaxen indirectly to get ant
xdocs/proposal to build.
Antoine
[1] http://gump.covalent.net/log/jaxen-from-packaged-dom4j.html
[2] http://lsd.student.utwente.nl/gump/jaxen/index.html
Re: jaxen does not build in some gump instances
Posted by Scott Sanders <sc...@dotnot.org>.
Let me take a look from your description.
Scott
On Jan 19, 2004, at 10:40 AM, Stefan Bodewig wrote:
> On Mon, 19 Jan 2004, Scott Sanders <sc...@dotnot.org> wrote:
>
>> I am a jaxen developer, and have been unable to split the jaxen
>> build to accomodate. All communication to the dom4j list has
>> returned nothing, so we are stuck with packaged builds.
>
> Scott, we already have a version that tries to build jaxen from a
> packaged dom4j. The other way around doesn't work as dom4j doesn't
> build against the latest jaxen release, it requires a more recent CVS
> version.
>
> This jaxen build doesn't pass either because of some jdom changes, see
> [1] - is there anything you could do about it? If so, the sequence
> would be (1) build jaxen from packaged dom4j, build (2) dom4j from this
> jaxen, (3) build jaxen - the one everybody is going to use - from (2).
>
> Footnotes:
> [1]
> http://lsd.student.utwente.nl/gump/jaxen/jaxen-from-packaged-
> dom4j.html
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
>
Re: jaxen does not build in some gump instances
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 19 Jan 2004, Scott Sanders <sc...@dotnot.org> wrote:
> I am a jaxen developer, and have been unable to split the jaxen
> build to accomodate. All communication to the dom4j list has
> returned nothing, so we are stuck with packaged builds.
Scott, we already have a version that tries to build jaxen from a
packaged dom4j. The other way around doesn't work as dom4j doesn't
build against the latest jaxen release, it requires a more recent CVS
version.
This jaxen build doesn't pass either because of some jdom changes, see
[1] - is there anything you could do about it? If so, the sequence
would be (1) build jaxen from packaged dom4j, build (2) dom4j from this
jaxen, (3) build jaxen - the one everybody is going to use - from (2).
Footnotes:
[1] http://lsd.student.utwente.nl/gump/jaxen/jaxen-from-packaged-dom4j.html
Stefan
Re: jaxen does not build in some gump instances
Posted by Scott Sanders <sc...@dotnot.org>.
On Jan 19, 2004, at 9:24 AM, Stefan Bodewig wrote:
> On Mon, 19 Jan 2004, Antoine Lévy-Lambert <an...@antbuild.com>
> wrote:
>
>> On some gump instances, the build of jaxen is failing (see
>> footnotes).
>
> I don't think Jaxen builds on any Gump instances.
This is correct. Jaxen and dom4j will not build on Gump since there is
a circular dependency between the two. I am a jaxen developer, and
have been unable to split the jaxen build to accomodate. All
communication to the dom4j list has returned nothing, so we are stuck
with packaged builds.
> Scott
Re: jaxen does not build in some gump instances
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 19 Jan 2004, Antoine Lévy-Lambert <an...@antbuild.com>
wrote:
> On some gump instances, the build of jaxen is failing (see
> footnotes).
I don't think Jaxen builds on any Gump instances.
> I am an ant developer, and I need jaxen indirectly to get ant
> xdocs/proposal to build.
Use packaged-jaxen instead of jaxen.
Stefan
Re: jaxen does not build in some gump instances
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> I am interested in seeing jaxen build in gump.
So am I. I'm told there is a circular dependency with DOM4J & (from folks
who've tried) it needs for code in DOM4J to move to Jaxen, and vice-verse,
in order to get fixed. For some reason the DOM4J/Jaxen communities don't
seem able to make this happen. I really wish this could be fixed, but this
is the third of fourth time I've heard about it w/o seeing any action.
regards
Adam