I have what amounts to an aggregator pom that I use to create an assembly
of a few different jars.
I do this by having my aggregator depend on the jars I want in my zip and
using a dependencySet in my assembly descriptor. It seems that
assembly:assembly only actually puts anything in the zip i
I'm a little late on this thread, but as mentioned, there has been some
discussion about eclipse and Maven in recent weeks. There is an
enhancement request for eclipse
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=109937), as well as
previous messages both on this list and on the eclipse pde-
Yes, I'm actually working for Jeff, so I'm investigating this in a general
sense. Unfortunately I'm new to both maven and pde-build so I'm still
trying to get a handle on the problem.
-Andrew
Brett Porter <[EMAIL PROTECTED]> wrote on 09/14/2005 09:49:42 PM:
> FWIW, I have been discussing build
to produce multiple
> artifacts that you can use as a dependency seperately within another
> project?
>
> are these projects really subprojects in one project with a shared root
> pom.xml file?
>
> or are they discrete projects,,,?
>
> bit more info would be grand :)
&g
The resulting artifact of a project A is a directory containing jar files,
binaries and resources and I package this in a jar, or even a zip or rpm
(if I had such a packaging plugin)
A jar/zip/rpm
- nested1.jar
- nested2.jar
- resources/binaries
- META-INF/manif
Jason van Zyl <[EMAIL PROTECTED]> wrote on 09/07/2005 05:29:45 PM:
>
> Might you have an ViewCVS URL of an example plugin, or set of plugins,
> that we can work against while discussing this?
It was suggested on the eclipse pde-build mailing list that building the
eclipse plugins that make up th
I have started looking at what would need to be done in order to build
Eclipse plugins using Maven 2.
The general idea is that POM files could be generated using information in
the plugins' manifest.mf, plugin.xml and build.properties files. At first
glance, the required information consists
