maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From olivier.lamb...@smals-mvm.be
Subject Fw: Missing dependencies in APP-INF/lib when releasing on a master project
Date Wed, 28 Feb 2007 11:53:42 GMT
Hi all,

I have a tricky issue with maven-release-plugin (but it's perhaps due to 
another plugin).

Here is the project structure:
Master (packaging is pom)
* CORE (packaging is jar)
* EJB (packaging is ejb, depend on the CORE and on commons-collection)
* EAR (packaging is ear, depend on the EJB to include it in the enterprise 
archive)

When I execute the 'release:perform' goal on the EAR project, everything 
works fine, the content of the ear file generated is something like that:
APP-INF
* lib
*  * commons-collection
*  * core
META-INF
ejb.jar

The problem is : When I execute the 'release:perform' goal on the Master 
project (to make a release of the master and all the components together), 
the content of the EAR does not include the internal dependency to the 
core project. So the content of the EAR is
APP-INF
* lib
*  * commons-collection
META-INF
ejb.jar

In the debug log of Maven, I can clearly see that maven does not try to 
resolve the dependency to the CORE ... why ??

Can someone help ?

Thanks
Oli
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message