Hello,
"Wojciech Biela" <[EMAIL PROTECTED]> writes:
>
> Well, I definitely have something wrong. I thought it though and I
> think my problem is different. My pom is quite complicated, as is my
> building process. In the master project I use the
> dependency-maven-plugin to add binary builds of the submodules to some
> custom structure:
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>dependency-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <phase>package</phase>
> <goals>
> <goal>copy</goal>
> </goals>
> <configuration>
> <artifactItems>
> <artifactItem>
> <groupId>${project.groupId}</groupId>
> <artifactId>SubModule1</artifactId>
> <version>${project.version}</version>
> <type>mod</type>
> <outputDirectory>${mod-dir}</outputDirectory>
> </artifactItem>
> </artifactItems>
> .....
>
> The problem is that this is executed BEFORE the submodules are
> built,
That's normal: maven builds parent before children. Your problem may
appear to be better handled by the maven-assembly-plugin which can
aggregate various parts rof a project's modules. Or you may want to
call your plugin outside base build:
$> mvn package
$> mvn dependency:copy // sure this is wrong but get the idea
regards
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
