Well... to answer part of my own question: I noticed that this happens in the
case that I have two different modules which each use the assembly plugin.
Somehow the plugin can't resolve both pre-defined assemblies in the modules.
They're different assemblies which I reference using <descriptorRef>, and as
soon as I comment out one of the plugin configurations, the whole project
builds again.
Does this have anything to do with being only able to defined a plugin once in
a POM and having to define separate executions? How can I solve this?
Any hint, especially from the Assembly developers ;-) is greatly appreciated!
Best regards,
Eric
P.S.
Here are my two POM excerpts:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<dependencies>
<dependency>
<groupId>ch.ipi</groupId>
<artifactId>ipi-assembly-xml-schemas</artifactId>
<version>${ipi-assembly-xml-schemas.version}</version>
</dependency>
</dependencies>
<executions>
<execution>
<id>create-xml-schema-jar</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>xml-schemas</descriptorRef>
</descriptorRefs>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<dependencies>
<dependency>
<groupId>ch.ipi</groupId>
<artifactId>ipi-assembly-batch</artifactId>
<version>${ipi-assembly-batch.version}</version>
</dependency>
</dependencies>
<executions>
<execution>
<id>create-batch-distribution</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>batch</descriptorRef>
</descriptorRefs>
</configuration>
</execution>
</executions>
</plugin>
-----Ursprüngliche Nachricht-----
Von: Lewis, Eric [mailto:[email protected]]
Gesendet: Montag, 7. Juni 2010 08:29
An: Maven Users List
Betreff: AW: Dependency fails, but only in reactor build
Anyone? :-)
Best regards,
Eric
-----Ursprüngliche Nachricht-----
Von: Lewis, Eric [mailto:[email protected]]
Gesendet: Mittwoch, 2. Juni 2010 11:52
An: [email protected]
Betreff: Dependency fails, but only in reactor build
Hi
I'm having problems with a dependency that can't be found, but only in a
reactor build.
We have a project 'activity' with several modules, one of them being the
'activity-client', which uses an assembly 'batch' (a ZIP for a batch client).
We have Hudson as CI server and build every project on commit changes: The
'activity' project builds flawlessly.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [source:jar-no-fork {execution: attach-sources}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-sources.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
...
[INFO] Building zip:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-batch.zip
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 30 seconds
[INFO] Finished at: Wed Jun 02 11:35:03 CEST 2010
[INFO] Final Memory: 76M/631M
[INFO] ------------------------------------------------------------------------
However, we also have a nightly build which builds the whole system with all
projects in one big reactor build.
Here, for some strange reason, the 'batch' assembly can't be found.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/esv-projects-tests__development/workspace/activity/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error reading assemblies: Descriptor with ID 'batch' not found
If within the checked out whole system I go to the directory of
'activity-client' and build it with 'mvn clean package', everything works.
If I do an 'mvn clean package' on the whole system, I get the error above.
So, clearly, the dependency exists in the repository. But sometimes it can't be
found...
How can that be or how can I check in a better way what's going wrong?
Best regards,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
