Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.0.6
-
None
-
None
-
jdk1.4
Description
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).