On Thu, 4 Aug 2005, Jason Grant wrote:
Take a look at the assembly plugin. It has the ability to produce
a jar with all dependencies unpacked.
So, you'd create a project containing 2 dependencies: one on the
eclipse.zip, and the other on your additions. Then call assembly:assembly,
feeding it this file 'all.xml':
<assembly>
<id>all</id>
<formats>
<format>jar</format><!-- or zip -->
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<dependencySets>
<dependencySet>
<outputDirectory>/</outputDirectory>
<unpack>true</unpack>
<scope>runtime</scope>
</dependencySet>
</dependencySets>
</assembly>
-- Kenney
> I would value tips on how to tackle the following. My repository
> contains a zip distribution (it's the Eclipse IDE), and I want my final
> build output to be a new zip file with the original contents plus jars
> that are produced from my source code.
>
> Being new to maven (I need to use maven2) I'm unclear about:
>
> 1) Whether depending/pulling/unpacking the original zip from the repo
> can be expressed in terms of (a) native POM constructs and (b) existing
> plugin goals? Or will I need to write my own plugin to acquire/unpack
> the zip? If the latter, is use of ant via marmalade a concise choice?
>
> 2) What is best practice for locating the unpacked zip filesystem? e.g.
> should it reside in the target area?
>
> 3) How do I tell maven to place my output jars in the unpacked zip
> filesystem?
>
> 4) How would I configure maven to produce a zip of the new filesystem as
> the project's output?
>
> Tips appreciated,
>
> Jason.
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
