i found this link helpful http://propellors.net/maven/book/assemblies.html
the maven site defines elements used in source node here http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_moduleSources repositories feature of assemblies would work for a multi-module project. so we're on the same page what do you considered a module also does multi-module have some defining characteristic? here is an early discussion of Maven module from Brett Porter circa 2005 http://docs.codehaus.org/display/MAVEN/Improves+Modules+Definition where the only definining characteristic is groupId,artifactId and version Here is Glassfish definition of module Module Definition At high level, a module is defined by the following information. key description example name Name of the component com.sun.module version Version number of the module 1.2.1-rc4 imports list of imported component, comma separated com.sun.bar com.sun.myothermodule exports list of classes or packages exported com.sun.module.spiwhere name is analogous to artifactId and exports list is analogous to groupId https://hk2.dev.java.net/modules.html would wither of these definitions conform to your understanding of module ? thanks, Martin ______________________________________________ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas. Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett. Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs. Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Sat, 16 May 2009 07:43:59 -0700 > From: [email protected] > To: [email protected] > Subject: Re: [maven 2] assembly: repository from multiple modules > > > Thanks Brian, this led me on the right path. Still... it'd be nice if the > repositories feature of assemblies would work for a multi-module project. > > So I ended up with this in my parent pom: > > <plugin> > <artifactId>maven-dependency-plugin</artifactId> > <configuration> > <copyPom>true</copyPom> > <useRepositoryLayout>true</useRepositoryLayout> > </configuration> > </plugin> > > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <version>2.2-beta-3</version> > <configuration> > <finalName>m2-repo</finalName> > <appendAssemblyId>false</appendAssemblyId> > <descriptors> > <descriptor>src/maven-assembly-repo.xml</descriptor> > </descriptors> > </configuration> > </plugin> > > and my maven-assembly-repo.xml descriptor looks like this: > <assembly xmlns="http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/assembly-1.0.0.xsd";> > <id>repository</id> > <formats> > <format>zip</format> > </formats> > <includeBaseDirectory>false</includeBaseDirectory> > <moduleSets> > <moduleSet> > <sources> > <includeModuleDirectory>false</includeModuleDirectory> > <fileSets> > <fileSet> > <directory>target/dependency</directory> > </fileSet> > </fileSets> > </sources> > </moduleSet> > </moduleSets> > </assembly> > > Thanks everyone for trying to help. BTW... it DID occur to me to > temporarily use an empty local repo and then zip it when I'm done with a > build. That would be pragmatic to get a solution quick but it felt a bit > sloppy and I wanted a better solution. > > ~ David Smiley > > > BRIAN FOX-5 wrote: > > > > The dependency:copy-dependencies can also produce a repository layout. > > Surely some combination of that plus assembly to zip it up should work. > > > > On Fri, May 15, 2009 at 3:39 PM, David Smiley @MITRE.org > > <[email protected]>wrote: > > > >> > >> Any update to this? I've tried a bunch of combinations. I think at this > >> point I'm going to try and hack the latest source to meet my needs. > >> > >> ~ David > >> > >> > >> Hal Hildebrand-3 wrote: > >> > > >> > I have a large, multiple module project that I need to create a > >> repository > >> > assembly for. I have no problems creating the binary, including the > >> > dependencies. However, I can't seem to create a repository. I'm > >> running > >> > the > >> > assembly in the project's top level pom, of course, but from what I can > >> > tell, there seems to be no way to indicated to use all the sub modules > >> - > >> > i.e. The only way to create the repository seems to be be placing all > >> the > >> > dependencies in the top level pom. Obviously, this will be a nightmare > >> to > >> > maintain. Also, since the binary assembly seems perfectly capable of > >> > including the sub module's binaries and dependencies, it would seem > >> that > >> > the > >> > repository assembly should be able to do the same. > >> > > >> > Falling short of actually creating the repository for one reason or > >> > another, > >> > if I could get the format of the binary assembly to be identical to the > >> > repository layout, that would be sufficient for my needs as I don't > >> need > >> > the > >> > maven repository metadata. Right now, I've tried using no outputfile > >> > format, with simply a directory - doesn't work. I've also tried using: > >> > ${groupId}/${artifactId} as the directory - kind of works, but now I > >> have > >> > .'s instead of /'s in the repository group id directory. > >> > > >> > Surely this is possible through some machination or incantation, right? > >> > > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/-maven-2--assembly%3A-repository-from-multiple-modules-tp8505848p23566098.html > >> Sent from the Maven - Users mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/-maven-2--assembly%3A-repository-from-multiple-modules-tp8505848p23574391.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > _________________________________________________________________ Hotmail® has a new way to see what's up with your friends. http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009
