this is exactly what i'm using right now, but I'm looking for more:) basically, what I'm looking for is a "hypothetical" "zip" packaging type, which would just cut a zip as specified (by probably using assembly plugin) and get it deployed to repository as there is nothing to compile and test for that module. I might end up using "deploy-file" to accomplish it manually ...
On 10/8/07, Mark Struberg <[EMAIL PROTECTED]> wrote: > > Hi! > > What about the maven-assembly-plugin? > > It is very simple to use, and you can specify exactly > what to zip. > > http://maven.apache.org/plugins/maven-assembly-plugin/ > > what do u need: > > 1st the plugin: > <!-- create the > ${artifactId}-${version}-resources.zip during the > packaging --> > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <configuration> > <descriptors> > > <descriptor>src/assembly/config-resources.xml</descriptor> > > <descriptor>src/assembly/sql-resources.xml</descriptor> > </descriptors> > </configuration> > <executions> > <execution> > <id>make-assembly</id> > <phase>package</phase> > <goals> > <goal>attached</goal> > </goals> > </execution> > </executions> > </plugin> > > > 2nd you need the assembly descriptors. here is an > example (src/assembly/sql-resources.xml): > <assembly> > <id>sql-resources</id> > <includeBaseDirectory>false</includeBaseDirectory> > <formats> > <format>zip</format> > </formats> > <fileSets> > <fileSet> > <directory>sql</directory> > <outputDirectory>sql</outputDirectory> > <includes> > <include>**/*.*</include> > </includes> > <excludes> > <exclude>CVS</exclude> > <exclude>**/misc/**/*.*</exclude> > </excludes> > </fileSet> > </fileSets> > </assembly> > > Hope this is what u need. > > LieGrü, > strub > > --- Yan Huang <[EMAIL PROTECTED]> schrieb: > > > Hello, > > > > I have these requirements to package a module: > > > > - it's group ID is different from what I have at > > the top level > > - no compilation or test is required > > - it just needs to be packaged in "zip" format > > - it needs to be deployed to a maven2 repository > > as part of deploy > > phase > > > > Do you think I need to separate this module out from > > the overall package > > because of different group ID? If I need to build it > > separately, what's > > going to be the "packaging" type? Maven does not > > support "zip" packaging > > type though, and I don't want an empty jar being > > created in order to attach > > "zip" file in the "package" phase by using assembly > > plugin. > > > > Any thoughts or suggestions? > > > > Thanks > > Yan > > > > > > Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und > viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
