Magic - packaging jars for distribution
Cameron Taggart <[email protected]>
| Newsgroups | gmane.comp.jakarta.avalon.user |
|---|---|
| Message-ID | <[email protected]> |
I'm trying to prepare the xsd2jibx 0.2 alpha release and I'm wondering
what the best approach would be for distributing the jars. I would like
to package both the transitive runtime dependencies and buildtime
dependencies. It would be nice to have an <x:fileset/> similar to
<x:path/>. Here is what I'm stuck what I'm working with at the moment
to put the dependencies in a "lib" directory.
<target name="dist" depends="clean, package">
<x:property name="version" feature="version"/>
<x:property name="xpp3.path" key="xpp3" feature="path"/>
<x:property name="jaxme-js.path" key="jaxme-js" feature="path"/>
<zip destfile="target/deliverables/${ant.project.name}-${version}.zip">
<zipfileset prefix="${ant.project.name}-${version}/lib"
dir="${magic.cache}"
includes="${xpp3.path}, ${jaxme-js.path}"/>
</zip>
</target>
.I think this could be improved with a <x:fileset/>. An <x:fileset>
would come in really handy when I go to build a web appliation resource
(WAR) file as well.
cheers,
Cameron
>>>> Example 1: Create an ant path composed of the transitive runtime
>>>> dependencies for the current project.
>>>>
>>>> <x:path id="path"/>
>>>>
>>>> Example 2: Create an ant path composed of the target artifact and its
>>>> full transitive runtime dependencies.
>>>>
>>>> <x:path id="path" key="avalon-meta-tools"/>
>>>>
>>>> I'm updated dpml now so you can either do an 'ant setup' or jump down
>>>