You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/12/18 14:12:20 UTC
[jira] Closed: (MNG-2946) Module-by-Profile seems to break plugin
dependencies
[ http://jira.codehaus.org/browse/MNG-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-2946.
-----------------------------
Assignee: Brett Porter
Resolution: Duplicate
Fix Version/s: (was: Reviewed Pending Version Assignment)
> Module-by-Profile seems to break plugin dependencies
> ----------------------------------------------------
>
> Key: MNG-2946
> URL: http://jira.codehaus.org/browse/MNG-2946
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.6
> Environment: jdk1.4
> Reporter: Daniel Takai
> Assignee: Brett Porter
>
> Using Module-by-Profile i ran into a problem with dependencies. My pom looks like this:
> <profiles>
> <profile>
> <id>default</id>
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> <modules>
> <module>module1</module>
> <module>module2</module>
> <module>module3</module>
> </modules>
> </profile>
> <profile>
> <id>integration</id>
> <modules>
> <module>module1</module>
> <module>module2</module>
> <module>module3</module>
> <module>integration</module>
> </modules>
> </profile>
> </profiles>
> The integration module runs the integration tests.
> The integration module contain an antrun plugin.
> Running the build on the integration module only works fine.
> Running it from the parent project using the integration profile breaks the build. The problem is that the plugin dependencies are not accessible to the ant build files (and therefore, i suppose, to the plugin).
--
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