Return-Path: 
 <dev-return-22726-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 42624 invoked from network); 8 Dec 2007 15:43:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 Dec 2007 15:43:27 -0000
Received: (qmail 70495 invoked by uid 500); 8 Dec 2007 15:43:16 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 70448 invoked by uid 500); 8 Dec 2007 15:43:16 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 70437 invoked by uid 99); 8 Dec 2007 15:43:15 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Dec 2007 07:43:15 -0800
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [62.179.121.48] (HELO viefep28-int.chello.at) (62.179.121.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Dec 2007 15:43:17 +0000
Received: from felixknecht.ch ([217.162.149.243]) by viefep28-int.chello.at
          (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP
          id <20071208154256.VVWQ9569.viefep28-int.chello.at@felixknecht.ch>
          for <dev@directory.apache.org>; Sat, 8 Dec 2007 16:42:56 +0100
Received: (qmail 25571 invoked by uid 210); 8 Dec 2007 15:42:54 -0000
Received: from 192.168.1.97 by odin (envelope-from <felixk@apache.org>,
 uid 201) with qmail-scanner-2.01st
 (clamdscan: 0.91.2/5031. perlscan: 2.01st.  
 Clear:RC:1(192.168.1.97):.
 Processed in 0.031761 secs); 08 Dec 2007 15:42:54 -0000
Received: from unknown (HELO ?192.168.1.97?) (192.168.1.97)
  by 192.168.1.11 with SMTP; 8 Dec 2007 15:42:54 -0000
Message-ID: <475ABB7E.8060304@apache.org>
Date: Sat, 08 Dec 2007 16:42:54 +0100
From: Felix Knecht <felixk@apache.org>
Organization: apache.org
User-Agent: Thunderbird 2.0.0.9 (X11/20071116)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Studio Maven Build
References: <4757146D.4080207@apache.org> <47586FF6.30304@apache.org>
 <4758E4FD.5060700@apache.org> <475AA0E2.3000601@apache.org>
In-Reply-To: <475AA0E2.3000601@apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Stefan Seelmann schrieb:
> Hi Felix,
> 
>> mvn
>> - 'install' is needed because some plugin projects are referencing
>> studio-dsml-parser witch doesn't already exists in local mvn repository
>> on first run.
>> - 'eclipse:eclipse' creates the .project and .classpath files in the
>> module folders
>> - 'studio.eclipse' adapts the .classpath to have entries like
>> <classpathentry path="lib/commons-io-1.3.1.jar" exported="true"
>> kind="lib"/> and adapts the 'Bundle-ClassPath' entry in the manifest.mf
>>
> 
> I just found one option for the eclipse:eclipse goal:
> 
> <pde>true</pde>
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#pde
> 
> It seems it makes something similar like the studio:eclipse goal.
> 

Almost yes. I played with it too, but I wasn't able to add the 'lib' directory prefix. To copy the needed dependencies
to the studio/{plugin}/lib directory we can use the maven-dependency-plugin as a workaround but to add then the right
path to the MANIFEST.MF I haven't found any solution using the pde option.
That's why I created the goal studio:eclipse - copy the nonscoped 'provided' dependencies to the lib directory (instead
of using the workaround) and adapt the Bundle-ClassPath in the Manifest file. I prefere a solution where you only need
to change the dependencies in the pom instead of one you need to make the changes as well in the manifest file. And even
then is still the open point what to do with the prefixing directory 'lib'. We can skip it and have the jar files in the
root of the created jar file like e.g. for studio-jars:

felix@donar ~/svn/apache/directory/maven-studio/studio-jars $ jar ft target/org.apache.directory.studio.jars-1.0.0.jar
META-INF/
META-INF/MANIFEST.MF
antlr-2.7.7.jar
shared-ldap-0.9.8-SNAPSHOT.jar
shared-ldap-constants-0.9.8-SNAPSHOT.jar
studio-dsml-parser-0.4.1.jar
shared-asn1-0.9.8-SNAPSHOT.jar
commons-collections-3.2.jar
dom4j-1.6.1.jar
nlog4j-1.2.25.jar
xpp3-1.1.3.4.O.jar
META-INF/LICENSE
META-INF/NOTICE

instead of the now existing

felix@donar ~/svn/apache/directory/maven-studio/studio-jars $ jar ft target/org.apache.directory.studio.jars-1.0.0.jar
META-INF/
META-INF/MANIFEST.MF
lib/
lib/antlr-2.7.7.jar
lib/shared-ldap-0.9.8-SNAPSHOT.jar
lib/shared-ldap-constants-0.9.8-SNAPSHOT.jar
lib/studio-dsml-parser-0.4.1.jar
lib/shared-asn1-0.9.8-SNAPSHOT.jar
lib/commons-collections-3.2.jar
lib/dom4j-1.6.1.jar
lib/nlog4j-1.2.25.jar
lib/xpp3-1.1.3.4.O.jar
META-INF/LICENSE
META-INF/NOTICE


If the lib prefix isn't absolutely needed or if you find a solution to prefix using the pde option  I'm absolutely +1
using the pde option and not having our own plugin for this.

Felix


> I'll experiment with it a bit...
> 
> Regards,
> Stefan
>