I have resolved the issue by not using wildcards in the include element,
but rather specify all modules explicitly. Seems I was running the 2.1
version of the assembly plugin, while it's fixed for 2.2...
For those interested, here's my src/main/assembly/assembly.xml:
<?xml version="1.0" encoding="UTF-8"?>
<assembly>
<formats>
<format>jar</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<moduleSets>
<moduleSet>
<includes>
<include>proj:proj-core</include>
</includes>
<binaries>
<unpack>true</unpack>
</binaries>
</moduleSet>
<moduleSet>
<includes>
<include>proj.othermodule:proj-othermodule</include>
</includes>
<binaries>
<unpack>false</unpack>
</binaries>
</moduleSet>
</moduleSets>
</assembly>
A more elegant and reusable way would be to use wildcards to include all
modules and exclude the core module.
-hg
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 10. januar 2007 13:34
To: [email protected]
Subject: [m2] Creation of jar artifact for pom type
Hi,
I 'm porting to a multimodule project with a config resembling:
proj (packaging: pom)
|- proj-core (type: jar)
||- NumberOne.class
|- proj-othermodule (type: jar)
||- NumberTwo.class
I was wondering how to (best) create a proj-1.0-SNAPSHOT.jar artifact in
the parent project (proj) containing the contents of proj-core and
including proj-othermodule as a jar (not expanding it into the proj
jar). Can't seem to solve this elegantly - not at all really at this
point. I was hoping I wouldn't have to resolve to using ant for this.
Although proj has pom packaging, I can't see this structure violating
the Maven principle of one project, one artifact.
Intended structure for proj jar:
- NumberOne.class
|- lib
||- proj-othermodule-1.0-SNAPSHOT.jar
-hg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
