geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <>
Subject Re: [mevenide-dev] Help building eclipse plugins
Date Sat, 27 Aug 2005 20:33:48 GMT

On Aug 27, 2005, at 4:29 PM, Sachin Patel wrote:

> So, Gilles doesn't recommend modeling the build for the geronimo  
> eclipse plugins after the Mevenide plugin, as he thinks its grown  
> way too complex, plus it doesn't support OSGI bundles.  The  
> geronimo server adapter are already defined as OSGI bundles anyways  
> so this is problem as I wouldn't to revert away from OSGI as this  
> would force me to use deprecated Eclipse APIs.
> He mentions trying to use the maven-osgi-plugin, but the M2 version  
> of it, which of course Geronimo hasn't moved to M2 yet.  Will the  
> move to M2 be a post 1.0 item?

Don't worry about that.  We're planning to get to M2 at some point,  
and with the eclipse code in a subproject, the build is independent.   
So if you want to go down the M2 path, I'm all for it.  Anyone else  


> From: Gilles Dodinet <>
> Date: August 27, 2005 10:19:21 AM EDT
> To:
> Subject: Re: [mevenide-dev] Help building eclipse plugins
> Reply-To:
> sachin,
> right now maven-eclipse-eclipse-plugin is used in conjunction with  
> m1. however this plugin has grown big and now exposes too many  
> configuration properties and thus is now way too complex. besides  
> that it doesn't support osgi bundle packaged plugins so it may  
> probably not fit your needs. months ago i had started to  
> reimplement it targetting m2 but had no time to finish the task.  
> luckily enough matthew pryor has started too to write a m2 plugin  
> to build eclipse plugins (search maven-dev list for "help with  
> custom lifecyle" thread). i don't know the exact status of this  
> plugin though.
> another alternative could be to use maven-osgi-plugin - haven't  
> tried m1 version, m2 version' howto can be found here : http:// 
> (in particular it needs a modified maven-archiver- 
> plugin version) ; just to let you know: i'm experimenting a little  
> issue with inherited artifacts : if projectA inherits from projectB  
> and projectB declares dependency D with a scope of either compile  
> or runtime, D artifact will be bundled in projectA's osgi bundle  
> even it redeclares D with a scope of provided. i've played with it  
> only recently so i'm not sure yet how to fix it. in any case i'll  
> fill a issue against felix jira if i can't solve it.
> also if you're hesitating i'd recommend you to start with m2. last,  
> as you'd probably know eclipse forces you to use a flat layout - m2  
> supports this very well when defining module as  <module> ../child- 
> project-folder</module>
> hope this helps-
> -- gd
> Sachin Patel wrote:
>> Hi all,
>> I'm wanting to build and package a set of plugins and its feature  
>> using Maven.  I see that you all have done this successfully with  
>> Mavenide.  I'm experienced in Eclipse but a newbie to Maven, so  
>> would someone mind helping me get started with this?  I've pulled  
>> down the source and I'm looking at the following directory structure
>> goals-grabber
>> maven-eclipse-plugin-plugin
>> mevenide-config
>> mevenide-core
>> mevenide-eclipse-help
>> mevenide-feature
>> mevenide-grammer
>> mevenide-master
>> ... ... ...
>> I want to essentially use your infrastructure as a model.... Where  
>> should I start, what should I be looking at?
>> Thanks in advance
>> Sachin.

Geir Magnusson Jr                                  +1-203-665-6437

View raw message