hi,

   i just use the src\main\assembly\dep.xml to manage my assemblies[1]
but i am using the assembly:directory goal to package my artifacts
because i just need to put all artifacts in a certain directory.

   or am i not understanding your problem correctly?

[1] http://maven.apache.org/maven2/guides/mini/guide-assemblies.html

ciao!

On 11/5/05, Christian Schulte <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Could it be that the assembly plugin does not support multi-module
> projects correctly ?
> I have the following project structure:
>
> Root
> |--Module1
> |--Module2
> |--Module3
>
> So somewhere in Root's pom.xml I have
>
> <modules>
>   <module>Module1</module>
>   <module>Module2</module>
>   <module>Module3</module>
> </modules>
>
> I now want the assembly plugin to build a jar file of all three ModuleX
> jar files and it does not work. When I do mvn assembly:assembly it does
> not use the three modules. If I put
>
> <dependencies>
>   <dependency>
>      <groupId>groupId</groupId>
>      <artifactId>Module1</artifactId>
>   </dependcy>
>   <dependency>
>      <groupId>groupId</groupId>
>      <artifactId>Module2</artifactId>
>   </dependcy>
>   <dependency>
>      <groupId>groupId</groupId>
>      <artifactId>Module3</artifactId>
>   </dependcy>
> </dependencies>
>
> into Root's pom.xml Maven complains about cyclic dependencies. So if the
> <modules>...</modules> section already defines the modules as
> dependencies why does the assembly plugin not see them ? If this section
> would not introduce a dependency to the modules why should maven
> complain about the cyclic dependencies ? What is the correct way to use
> the assembly plugin then ?
>
> I looked at the source to see how things are intended to work. If I make
> the following change:
>
> [EMAIL 
> PROTECTED]:~/maven2-cvs/maven-site/maven-plugins/maven-assembly-plugin/src/main/java/org/apache/maven/plugin/assembly$
> svn diff
> Index: AbstractUnpackingMojo.java
> ===================================================================
> --- AbstractUnpackingMojo.java  (Revision 330942)
> +++ AbstractUnpackingMojo.java  (Arbeitskopie)
> @@ -130,7 +130,7 @@
>
>                  String key = artifact.getGroupId() + ":" +
> artifact.getArtifactId() + ":" + artifact.getVersion();
>
> -                if ( !reactorArtifacts.containsKey( key ) &&
> !dependencies.containsKey( key ) )
> +                if ( !dependencies.containsKey( key ) )
>                  {
>                      dependencies.put( key, artifact );
>                  }
>
>
> mvn assembly:assembly starts aggregating the contents of the jar files
> of the modules. There is just one thing which then still does not work
> and that are the different manifest files are lost and I get a default
> manifest in the assembled jar file. I definetly need help with this.
>
> --
> Christian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--

"Programming, an artform that fights back"

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to