[jira] Created: (MASSEMBLY-162) In a multiproject environment, assembly takes wrong dependencies

[M. van Leeuwen (JIRA)]

In a multiproject environment, assembly takes wrong dependencies


 Key: MASSEMBLY-162
 URL: http://jira.codehaus.org/browse/MASSEMBLY-162
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.1
Reporter: M. van Leeuwen
Priority: Critical


With a projectstructure like 'Project/{ejb,war,ear,client}' packaging the 
client as a fat jar-with-dependencies, it works fine using the following 
configuration.
=== etc/fatjar.xml 
fat
  jar
  false
  
  target/classes
  /

  

  /
  true
  runtime

  

=== pom.xml ===

  0.3-SNAPSHOT
  4.0.0
  mygroup
  myapp-client
  My Application
  

  



maven-assembly-plugin
2.1


etc/fatjar.xml


path.to.MainClass



package
assembly
  





But when I'm on the level above (packaging all) it just assembles all 
underlying dependencies into my clientjar, and not the dependencies of the 
childproject.

-- 
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

[jira] Commented: (MRELEASE-157) Share version for multi-module releases

[M. van Leeuwen (JIRA)]

[ http://jira.codehaus.org/browse/MRELEASE-157?page=comments#action_78031 ] 

M. van Leeuwen commented on MRELEASE-157:
-

I've no problem hitting ENTER several times, but it keeps ignoring my earlier 
input. It is not hard to remember the previous entered value and use it as a 
default in the next version question.

> Share version for multi-module releases
> ---
>
> Key: MRELEASE-157
> URL: http://jira.codehaus.org/browse/MRELEASE-157
> Project: Maven 2.x Release Plugin
>  Issue Type: New Feature
>Affects Versions: 2.0-beta-4
>Reporter: Joerg Schaible
>
> In our setup all artifacts of a multi-module setup share the same release. 
> Therefore it would be really good, if we could configure the plugin (e.g. 
> shareVersion=true) to ask once for the version to release and once for the 
> version to set after the release for all modules.

-- 
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

[jira] Commented: (MWAR-9) WAR plugin should support minimal WARs for inclusion within an EAR

[M. van Leeuwen (JIRA)]

[ http://jira.codehaus.org/browse/MWAR-9?page=comments#action_77928 ] 

M. van Leeuwen commented on MWAR-9:
---

Is adding a new scope not the easiest way? Just configure the dependency with 
scope 'ear' and it will not be included as jar in the WAR, but in the EAR. The 
plugin should without any configuration find these scoped dependencies and add 
them as a classpath entry to the manifest.

> WAR plugin should support minimal WARs for inclusion within an EAR
> --
>
> Key: MWAR-9
> URL: http://jira.codehaus.org/browse/MWAR-9
> Project: Maven 2.x War Plugin
>  Issue Type: Improvement
>Reporter: Mike Perham
>
> I noticed that when I build a WAR, I get a gigantic WEB-INF/lib with all my 
> deps.  This is fine for a default but maven should also support "skeleton" 
> WARs which will be packaged within an EAR.  We have EARs which package 3-4 
> WARs each and to have the deps duplicated within each WAR means we cannot 
> have shared data (since the classes are loaded within each WAR's classloader, 
> rather than by the parent EAR's classloader).  It also means 80MB EARs!  :-)
> It seems like two things need to happen:
> 1) Add a "skeleton" flag which prevents copying any dependencies to 
> WEB-INF/lib.
> 2) Instead generate a META-INF/MANIFEST.MF which has a Class-Path entry which 
> lists the relative locations of the dependencies within the parent EAR.
> Fabrice has basically the same idea written down here.  Starting with "- for 
> a War..." : 
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112737860024530&w=2

-- 
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