Yes, you could add a goal to your maven.xml file that specifies which dependencies are put into the fortress-complete.jar.
This snippet _should_ work, but I haven't tested it.
<snip snippet>
we currently have:
<postGoal name="java:jar">
<!-- build big jar -->
<ant:mkdir dir="${maven.build.dir}/libs"/>
<deploy:copy-deps
todir="${maven.build.dir}/libs"
excludes="junit,avalon-fortress-tools,ant,qdox,xalan"/><ant:jar destfile="${maven.build.dir}/${pom.artifactId}-complete-${pom.currentVersion}.jar" duplicate="preserve">
<ant:manifest>
<ant:attribute name="Extension-Name" value="${pom.aritfactId}-complete"/>
<ant:attribute name="Specification-Vendor" value="Apache Software Foundation"/>
<ant:attribute name="Specification-Version" value="${pom.currentVersion}"/>
<ant:attribute name="Implementation-Vendor" value="Apache Software Foundation"/>
<ant:attribute name="Implementation-Version" value="${pom.currentVersion}"/>
</ant:manifest>
<ant:zipfileset src="${maven.build.dir}/${maven.final.name}.jar"/>
<ant:zipgroupfileset dir="${maven.build.dir}/libs" includes="*.zip"/>
</ant:jar>
</postGoal>
(http://cvs.apache.org/viewcvs.cgi/avalon/fortress/container/maven.xml)
<j:if test="${dep.getProperty('jar.include')=='true'}">
this is nice though ;)
101 ways to do it :D
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
