[jira] Commented: (MANTTASKS-115) Plugin classpath problem in multi module maven project

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MANTTASKS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143663#action_143663 ] 

Dennis Lundberg commented on MANTTASKS-115:
-------------------------------------------

I think this might be filed in the wrong JIRA project.

Do you have a problem with maven-antrun-plugin?

> Plugin classpath problem in multi module maven project
> ------------------------------------------------------
>
>                 Key: MANTTASKS-115
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-115
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>    Affects Versions: 2.0.9
>         Environment: WindowsXP Pro 
> jdk1.5.0_11
>            Reporter: Alexandre GIGLEUX
>            Priority: Minor
>         Attachments: ProblemMavenPluginClasspath.zip
>
>
> We have a pom.xml with <modules> :
> 	<modules>
> 		<module>./Module1</module>
> 		<module>./Module2</module>
> 	</modules>
> In Module1 we use the define <dependencies>.
> In Module2 we also define <dependencies> for maven-antrun-plugin with other <dependency>.
> Problem when we display <echo message="plugin classpath:  ${plugin_classpath}" />, in Module2 we have the classpath of the Module1.
> The only workaround is to add specific <dependency> of Module2, in Module1 (for the maven-antrun-plugin plugin).
> It looks like the plugin classpath is not updated for each Module.

-- 
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