Bad news: jaxen is used in the core [1]
Good news: Arnaud had already upgraded a lot of deps and attached
patches (MAVEN-1797 - 1805), among them for jaxen [2]
Should we work on m1.1.1 with only upgraded deps?
:)
-Lukas
[1] http://maven.apache.org/maven-1.x/dependencies.html
[2] http://jira.codehaus.org/browse/MAVEN-1797
Arnaud HERITIER wrote:
Hi jeff,
What you have to check, it is if jaxen is loaded by the core. If that's
the case, the version in the core is always used.
If not, it is the version of jaxen used by the first plugin loaded which
use it.
That's why we tried for the 1.1 release of maven to align dependencies to
have less side effects.
I hope that 1.1.1 is compatible with 1.1-beta-9. Depending of the part of
jaxen which is used by pmd it's possible that it works fine with the old
version.
If it's not the case you'll have to try to upgrade jaxen everywhere...
Arnaud
On Nov 30, 2007 2:05 AM, Jeff Jensen <[EMAIL PROTECTED]>
wrote:
Hi Arnaud,
PMD 4.1 has updated its deps (e.g. asm and jaxen), and I am concerned on
upgrading the plugin. I know you (and possibly others) spent considerable
time aligning the dependencies amongst core and many other plugins. I
know
Jaxen was one of them.
Do you have concerns/suggestions on updating the plugin deps in this
manner
(e.g. jaxen from 1.1-beta-9 to 1.1.1)?
---------------------------------------------------------------------
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]
