Joerg Hohwiller wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[cut]
I do NOT use assembly, because I did NOT find it suiteable for my needs but
maybe I was missing something.
But I did not reinvent the wheel, too. I use the resources plugin and the
dependency plugin to build the complete structure of the package into
target/package/ROOT/ all with existing maven stuff.
So in src/main/resources/ROOT/usr/foo/... you dump everything you want to have
included as is. Then (in my case) there is src/main/templates/ROOT/usr/foo/...
for all filtered resources and via the dependency plugin you can copy all
reuqired jars to target/package/ROOT/usr/foo/lib/ or extract a war file to
target/package/ROOT/usr/foo/webapps/
But this is exactly the thing to clarify. How does this work with the assembly
plugin instead?
I have evaluated the assembly plugin and now I see the point. This gives you
another level of flexibility how to determine what goes into the package.
I will consider this when I update the solaris plugin...
Something that all these plugins should share in the end is a common part of the
documentation describing how to produce the stuff into the "target" folder
and some good examples.
This is still very much true.
A'hoy!
I'm picking up this old thread again now that I'm again facing the
tedious work of creating prototype files for Solaris packages.
I've made a goal in the Solaris plugin called generate-prototype which
you can configure like this:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>solaris-maven-plugin</artifactId>
<version>1.0-alpha-1-SNAPSHOT</version>
<executions>
<execution>
<phase>generate-resources</phase>
<goals>
<goal>generate-prototype</goal>
</goals>
</execution>
</executions>
<configuration>
<packageRoot>target/${artifactId}-${version}-dist</packageRoot>
<defaultUser>javabin</defaultUser>
<defaultGroup>javabin</defaultGroup>
<prototypeEntryCollections>
<prototypeEntryCollection>
<type>dir</type>
<mode>?</mode>
<user>?</user>
<group>?</group>
<includes>
<include>opt</include>
<include>opt/jb</include>
</includes>
</prototypeEntryCollection>
<prototypeEntryCollection>
<type>file</type>
<mode>0755</mode>
<includes>
<include>opt/jb/tips-handler/server/bin/*</include>
</includes>
</prototypeEntryCollection>
</prototypeEntryCollections>
</configuration>
</plugin>
and it will give you this:
d none /opt ? ? ?
d none /opt/jb ? ? ?
d none /opt/jb/tips-handler 0755 javabin javabin
d none /opt/jb/tips-handler/etc 0755 javabin javabin
f none /opt/jb/tips-handler/etc/config.properties 0664 javabin javabin
f none /opt/jb/tips-handler/etc/jetty-context.xml 0664 javabin javabin
f none /opt/jb/tips-handler/etc/log4j.properties 0664 javabin javabin
f none /opt/jb/tips-handler/etc/web-override.xml 0664 javabin javabin
d none /opt/jb/tips-handler/server 0755 javabin javabin
d none /opt/jb/tips-handler/server/bin 0755 javabin javabin
f none /opt/jb/tips-handler/server/bin/tipsserver 0755 javabin javabin
d none /opt/jb/tips-handler/server/repo 0755 javabin javabin
d none /opt/jb/tips-handler/server/repo/antlr 0755 javabin javabin
d none /opt/jb/tips-handler/server/repo/antlr/antlr 0755 javabin javabin
d none /opt/jb/tips-handler/server/repo/antlr/antlr/2.7.6 0755 javabin
javabin
f none
/opt/jb/tips-handler/server/repo/antlr/antlr/2.7.6/antlr-2.7.6.jar 0664
javabin javabin
f none
/opt/jb/tips-handler/server/repo/antlr/antlr/maven-metadata-appassembler.xml
0664 javabin javabin
...
many, many, lines of wonderful generated prototype stuff.
I took the liberty of committing the source code as it is only in an
alpha, but if you don't like it I can move it elsewhere.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
