Re: assembly - plugin

[Nick Stolwijk]

I guess you have to split up the commons-project into multiple modules 
and then just install them like a normal artifact. Why use the assembly 
plugin for such tasks?

With regards,
Nick Stolwijk

Matthias Marchart wrote:
I'm sorry, i subsribed to the list about 15 min. ago ;)
The solution seems not to fulfill my needs:

I've a commons-project and this is splitted up into subprojects by 
packagenames. This commons-project is completly independend of the projects 
which need to include it (into an ear-file). I'd like to include a subset of 
packages into that ear as an ejb3Module.

<ejb3Module>
     <artifactId>common-mysubset</artifactId>
     <groupId>org.domain.common</groupId>
     <bundleFileName>common.jar</bundleFileName>
</ejb3Module>

-------- Original-Nachricht --------
  
Datum: Wed, 05 Sep 2007 10:53:50 +0200
Von: Nick Stolwijk <[EMAIL PROTECTED]>
An: Maven Users List <users@maven.apache.org>
Betreff: Re: assembly - plugin
    

  
Yes, and the answer was given an hour ago to someone else's post. To
quote:

Hi,

Evan Toliopoulos schrieb:
    
Hi,

I am having trouble deploying a 'tar.gz' assembly of a parent project
using the deploy goal.

The parent project has a number of child module projects.

Essentially I am running the following on the parent project:

    mvn package assembly:assembly deploy
      
What is happening here is this: First 'assembly:assembly' is executed as 
a standalone plugin goal on the command line, which builds the assembly. 
Then as the second step the 'deploy' phase is invoked on your project, 
and since these two steps are two completely separate executions, the 
second run (deploy) knows nothing about the previously build assembly.

What you should do instead, is to attach the assembly-plugin execution 
to the build lifecycle of your project, so it gets executed 
automatically when you run 'mvn deploy' for example. To do this modify 
your plugin configuration like this:

  [...]
  <plugin>
    <artifactId>maven-assembly-plugin</artifactId>
    <inherited>false</inherited>
    <configuration>
      <descriptors>
        <descriptor>src/main/assembly/developer-assembly.xml</descriptor>
      </descriptors>
    </configuration>
    <executions>
      <execution>
        <id>make-assembly</id>
        <phase>package</phase>
        <goals>
          <goal>single</goal>
        </goals>
      </execution>
    </executions>
  </plugin>
  [...]

This executes the assembly-plugin as part of the 'package' phase of the 
project and attaches the built assembly to your project, the deploy 
plugin then will automatically pick up this additional artifact and 
deploy it to the repository.

-Tim

Matthias Marchart wrote:
    
Hello!

My questions concerns the assembly-plugin (see
      
http://maven.apache.org/plugins/maven-assembly-plugin/)
    
Is there a way to install the assembly's created during the package -
      
phase to the local repository?
    
I like to refer the assembly in a other project ... 

Thanks for your help!
Matthias
  
      
---------------------------------------------------------------------
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]