Return-Path: 
 <users-return-28604-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: (qmail 57236 invoked from network); 7 Sep 2005 20:59:56 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 7 Sep 2005 20:59:56 -0000
Received: (qmail 22538 invoked by uid 500); 7 Sep 2005 20:59:50 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 22514 invoked by uid 500); 7 Sep 2005 20:59:50 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 22501 invoked by uid 99); 7 Sep 2005 20:59:50 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 13:59:50 -0700
X-ASF-Spam-Status: No, hits=1.3 required=10.0
	tests=DNS_FROM_RFC_ABUSE,HTML_20_30,HTML_MESSAGE,SPF_HELO_FAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [32.97.182.144] (HELO e4.ny.us.ibm.com) (32.97.182.144)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 14:00:03 -0700
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e4.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j87KxiHe021531
	for <users@maven.apache.org>; Wed, 7 Sep 2005 16:59:44 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by d01relay02.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j87Kxipu084278
	for <users@maven.apache.org>; Wed, 7 Sep 2005 16:59:44 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1])
	by d01av02.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j87KxV1C011454
	for <users@maven.apache.org>; Wed, 7 Sep 2005 16:59:31 -0400
Received: from d25ml01.torolab.ibm.com (d25ml01.torolab.ibm.com [9.26.6.102])
	by d01av02.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j87KxUwM011432
	for <users@maven.apache.org>; Wed, 7 Sep 2005 16:59:30 -0400
In-Reply-To: <D1CC6849-0B98-480E-BF0B-0A645BFA0177@mac.com>
To: "Maven Users List" <users@maven.apache.org>
MIME-Version: 1.0
Subject: [m2] Building Eclipse plugins using Maven 2
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
From: Andrew Niefer <aniefer@ca.ibm.com>
Message-ID: 
 <OFC03F565E.41927965-ON85257074.006FC30F-85257075.0073551F@ca.ibm.com>
Date: Wed, 7 Sep 2005 16:58:41 -0400
X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.5.4|March 27,
 2005) at 09/07/2005
 16:58:41,
	Serialize complete at 09/07/2005 16:58:41
Content-Type: multipart/alternative;
 boundary="=_alternative 007354A385257075_="
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

--=_alternative 007354A385257075_=
Content-Type: text/plain; charset="US-ASCII"

 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
--=_alternative 007354A385257075_=--