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]
