[ http://jira.codehaus.org/browse/MAVEN-1435?page=all ]
Arnaud Heritier updated MAVEN-1435:
-----------------------------------
Fix Version: (was: 1.1-beta-3)
> Plugin classpath are not overwriting project classpath.
> -------------------------------------------------------
>
> Key: MAVEN-1435
> URL: http://jira.codehaus.org/browse/MAVEN-1435
> Project: Maven
> Type: Bug
> Reporter: Jose Peleteiro
> Priority: Critical
> Attachments: example.zip
>
>
> My project uses picocontainer 1.1 and andromda maven plugin uses
> picocontainer 1.0. In plugin´s project.xml there´s a pico 1.0 depedencie
> declaration, but as in my project there´s a pico 1.1 declaration so I cant
> run it.
> Okay, I´ve looked plugin code and I found:
> <j:new var="pluginUtils" className="org.andromda.maven.MavenPluginUtils"/>
> that uses pico 1.0 and I tried to find a way to set it´s context classpath,
> but I could not find it (Someway like ant).
> I´ve looked at project.xml and wrote
> "<properties><classloader>root</classloader></properties>" at pico 1.0
> depedency.
> It goes perfectly... well, not so perfectly because if I run another plugin
> that needs pico 1.1 (like xdoclet 2.0 will soon) I got problem because when I
> finish to run a plugin classpath configuration does not come back to normal.
> In my opinion if I write plugins depedencies should overwrite project
> depedencies when a plugin is running and just when its running.
> I wrote a example, there is two jars on this zip, one of them is my andromda
> cartridge and the andromda plugin with classloader fixed.
> test1 - Just run andromda plugin
> test2 - Run andromda plugin and other code that uses pico 1.1.
> test3 - Run a code that uses pico 1.1 and andromda plugin.
> Thank´s
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
