*ping*
Waking this thread up again. While it's bad for us to go "Jelly HEAD +
Jaxen HEAD -> can't work so turn off the build", it's much worse for
us to let the noise continue as that switches people off of paying
attention to the gump errors. It becomes background noise.
Of course this might be interpreted as a feature request for gump;
don't irritate us by repeating yourself, instead just send us a
summary every now and then of the ones that are long term issues.
Still, +1 to any idea that gets rid of the background noise.
Hen
On 12/10/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> It doesn't matter what Maven installation you use, I don't think, though
> IIRC Gump still uses 1.0.2 if that helps.
>
> I believe the failure is commons-jelly-tags-xml, not commons-jelly.
>
> Remember, gump uses the latest of everything, so you need to build the
> latests Jelly library snapshot and update the dependency of the tags to
> use that too.
>
> maven -X will reveal what libraries are actually in use.
>
> - Brett
>
> Paul Libbrecht wrote:
> >
> >
> > I'm trying hard to fail and fail to fail...
> > As I understand it would be enough to change
> > ${JELLY_HOME}/parent-project.xml to refer jaxen 1.1-beta-6, 1.1-beta-8
> > or 1.1-beta-5... but "maven clean jar" still succeeds with me.
> >
> > Can it be this is related to the maven classpath ??
> > Am I understanding something wrong of Gump or this should not be set and
> > maven should proceeding using its own classpath ?? (in my
> > maven-1.1-beta-2, this is only forehead.jar which itself builds other
> > classloaders based on maven-home).
> >
> > paul
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
