> -----Original Message-----
> >> Lastly, what about creating the "BIG JAR" where all of Fortress's
> >> dependencies were included?
> > what about it?
> Can we still do it?
>
Do you mean fortress-complete?
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. Just run "maven
jar:jar" and you'll end up building a fortress-complete-1.0.jar along with
your normal fortress-1.0.jar
[goes in maven.xml]
<postGoal name="jar:jar">
<ant:delete dir="${maven.build.dir}/complete_tmp"/>
<ant:mkdir dir="${maven.build.dir}/complete_tmp"/>
<j:forEach var="dep" items="${pom.dependencies}">
<j:if test="${dep.getProperty('jar.include')=='true'}">
<ant:unjar
dest="${maven.build.dir}/complete_tmp"
src="${maven.repo.local}/${dep.artifactDirectory}/jars/${dep.artifact}"/>
</j:if>
</j:forEach>
<ant:unjar
dest="${maven.build.dir}/complete_tmp"
src="${maven.build.dir}/${maven.final.name}.jar"/>
<ant:jar
jarfile="${maven.build.dir}/${pom.artifactId}-complete-${pom.currentVersion}
.jar"
basedir="${maven.build.dest}"
index="true"/>
<ant:delete dir="${maven.build.dir}/complete_tmp/"/>
</postGoal>
Also, this goal expects you to specify which dependencies are included in
the fortress-complete.jar file by adding a "jar.include" property:
[project.xml snippet]:
<dependency>
<groupId>framework</groupId>
<artifactId>avalon-framework</artifactId>
<version>4.1.4</version>
<properties>
<jar.include>true</jar.include>
</properties>
</dependency>
jaaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
