You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andrew Niefer <an...@ca.ibm.com> on 2005/09/07 22:58:41 UTC
[m2] Building Eclipse plugins using Maven 2
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 of the dependencies (out of the
manifest or plugin.xml), the sources and resources (from
build.properties).
One of the first problems that arises is physical layout. An eclipse
workspace with a set of plugins that need to be considered at the same
time, these plugins do not necessarily reside in the same location on
disk.
We will want to treat these plugins as <modules/> under a common parent.
The first question then is for each module, do we copy all the sources &
resources into the normal maven layout, or do we create only the pom.xml
and point to the original locations using the <sourceDirectory/> and
<resource><directory/> tags.
Because an eclipse plugin can result in more than one jar file, we may
then have nested modules for each additional jar.
There will also be dependencies on plugins that exist in a target eclipse
installation instead of in the workspace. Jars for these plugins would
need to be placed into the local repository. POM files would also need to
be generated for these to specify their interdependencies.
The install phase would be different from the normal m2 install. We would
need to gather the jars and any additional resources into the standard
eclipse features & plugins directories. I have not yet looked into this.
I would welcome any comments people have,
-Andrew
Re: [m2] Building Eclipse plugins using Maven 2
Posted by Benedict Heal <bh...@benedictheal.com>.
This would be a wonderful idea.
I'd particularly welcome easy ways to run JUnit tests on plugins from maven.
good luck,
Benedict
Andrew Niefer wrote:
> 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 of the dependencies (out of the
>manifest or plugin.xml), the sources and resources (from
>build.properties).
>
>One of the first problems that arises is physical layout. An eclipse
>workspace with a set of plugins that need to be considered at the same
>time, these plugins do not necessarily reside in the same location on
>disk.
>We will want to treat these plugins as <modules/> under a common parent.
>The first question then is for each module, do we copy all the sources &
>resources into the normal maven layout, or do we create only the pom.xml
>and point to the original locations using the <sourceDirectory/> and
><resource><directory/> tags.
>
>Because an eclipse plugin can result in more than one jar file, we may
>then have nested modules for each additional jar.
>
>There will also be dependencies on plugins that exist in a target eclipse
>installation instead of in the workspace. Jars for these plugins would
>need to be placed into the local repository. POM files would also need to
>be generated for these to specify their interdependencies.
>
>The install phase would be different from the normal m2 install. We would
>need to gather the jars and any additional resources into the standard
>eclipse features & plugins directories. I have not yet looked into this.
>
>I would welcome any comments people have,
>
>-Andrew
>
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.0.344 / Virus Database: 267.10.18/91 - Release Date: 06/09/2005
>
>
Re: [m2] Building Eclipse plugins using Maven 2
Posted by dan tran <da...@gmail.com>.
What about from a pom.xml, maven can generate
manifest.fm<http://manifest.fm>file.
There is already some work done at
http://svn.apache.org/repos/asf/incubator/felix/trunk/tools/maven2/maven-osgi-plugin/
-D
On 9/7/05, Andrew Niefer <an...@ca.ibm.com> wrote:
>
> Jason van Zyl <ja...@maven.org> 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 the RCP would be a good place to start.
> In fact, Jeff's message,
> http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00076.html, is a
> likely a better starting point than mine.
>
> The ViewCVS URL for eclipse is http://dev.eclipse.org/viewcvs/index.cgi/
>
> If we started with org.eclipse.osgi which has no external dependencies,
> org.eclipse.core.runtime depends on osgi, and org.eclipse.swt introduces
> fragments as an interesting case.
>
> -Andrew
>
Re: [m2] Building Eclipse plugins using Maven 2
Posted by Andrew Niefer <an...@ca.ibm.com>.
Jason van Zyl <ja...@maven.org> 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 the RCP would be a good place to start.
In fact, Jeff's message,
http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00076.html, is a
likely a better starting point than mine.
The ViewCVS URL for eclipse is http://dev.eclipse.org/viewcvs/index.cgi/
If we started with org.eclipse.osgi which has no external dependencies,
org.eclipse.core.runtime depends on osgi, and org.eclipse.swt introduces
fragments as an interesting case.
-Andrew
Re: [m2] Building Eclipse plugins using Maven 2
Posted by Jason van Zyl <ja...@maven.org>.
On Wed, 2005-09-07 at 16:58 -0400, Andrew Niefer wrote:
> 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 of the dependencies (out of the
> manifest or plugin.xml), the sources and resources (from
> build.properties).
Might you have an ViewCVS URL of an example plugin, or set of plugins,
that we can work against while discussing this?
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org