Maven for Felix

["Richard S. Hall" <he...@ungoverned.org>]

I think we need to consider creating our Maven build process for Felix. 
I want to move the shell-related bundles out of the framework 
subproject, but this is dependent upon us having an overall build process.

The situation we have in the framework subproject right now is that 
three library JAR files (felix.jar, osgi.jar, moduleloader.jar) and 
three bundle JAR files (shell, shelltui, bundlerepository) are generated 
by the Ant build file. From our previous discussions, I believe our 
approach will be to combine the three library JAR files into one 
felix.jar file. The three bundles become their own subprojects.

Additionally, when you execute (i.e., "java -jar lib/felix.jar") the 
framework, it looks in lib/config.properties to get its configuration 
properties which include auto-start property that references the three 
shell-related bundles so that the framework starts up with an 
interactive shell. So this will have to be dealt with somehow too.

I currently have some uncommitted changes on the bundlerepository 
bundle, but I should commit them soon and then we will can go full force 
into creating the new build process. So, we need some people with good 
Maven know-how to get the ball rolling.

I had also thought that maybe we should set up a Felix "subproject 
template" subproject so that new subprojects can simply copy it into 
their directory...this might be helpful since we have a handful of 
outstanding contributions that will hopefully get their paperwork 
situations finalized soon.

Thoughts, suggestions?

Thanks in advance,

-> richard

Re: Maven for Felix

["Richard S. Hall" <he...@ungoverned.org>]

Timothy Bennett wrote:
> I can help get it started during the evenings this week.  Just let me 
> know when you want to freeze the code.

Great. I will let you know...should be soon.

> I still need to flatten the tools directory, so I'll do that at the 
> same time.

Ok.

>> I had also thought that maybe we should set up a Felix "subproject 
>> template" subproject so that new subprojects can simply copy it into 
>> their directory...this might be helpful since we have a handful of 
>> outstanding contributions that will hopefully get their paperwork 
>> situations finalized soon.
>
> I wonder if a maven archetype might help.

Don't know. Whatever works will be fine by me.

Thanks.

-> richard

Re: Maven for Felix

[Enrique Rodriguez <en...@gmail.com>]

On 2/21/06, Rinku <ra...@gmail.com> wrote:
> I have not followed the Felix's Maven-OSGi plugin for a quite some time
> now. Wondering (if and) how usable is it for Eclipse Plugin/RCP
> development since plugins are essentially OSGi bundles?

The plugin is not at all useful for Eclipse development; it's not
designed to be and I personally don't intend to take it in that
direction.  If you (and your entire development team) are standardized
on Eclipse, which I would assume if you are developing for Eclipse
RCP, then you are better off using the fine tooling in Eclipse.

The Felix M2 Plugin knows how to convert a project in the standard
on-disk M2 layout and package it into a bundle, with some rudimentary
support for deriving some of the OSGi manifest entries.  IMO, the
benefit of the plugin is to extend the M2 benefit of having POM
metadata and now OSGi bundle metadata together in one place, namely
the M2 pom.xml.

Further, the Felix M2 Plugin helps with IDE independence, for example
the ability to use Eclipse and IntelliJ on the same project team, as
is common on OSS projects ... with the caveat, of course, that you
have simply moved what you are standardizing on from an IDE to a build
tool.

> Is more work forthcoming on these lines? There was some discussion on
> the Maven mailing list about coordinating with Eclipse PDE team but I
> haven't run into any more updates on this.

I can't speak for general Maven team - Eclipse team coordination and
this is the wrong mailing list for that.  But, as for the plugin
maintained here, there is no additional Eclipse support planned.  At
most, on an as-requested/as-needed basis we'll add better support for
OSGi R4 manifest entries.

Enrique

Re: Maven for Felix

[Rinku <ra...@gmail.com>]

I have not followed the Felix's Maven-OSGi plugin for a quite some time 
now. Wondering (if and) how usable is it for Eclipse Plugin/RCP 
development since plugins are essentially OSGi bundles?

Is more work forthcoming on these lines? There was some discussion on 
the Maven mailing list about coordinating with Eclipse PDE team but I 
haven't run into any more updates on this.

Anyone on this list?

Thanks in advance,

Rahul

----- Original Message ----- 
From: "Alex Karasulu" <ao...@bellsouth.net>
To: <fe...@incubator.apache.org>
Sent: Tuesday, February 21, 2006 11:22 AM
Subject: Re: Maven for Felix


> Timothy Bennett wrote:
>
>> Richard S. Hall wrote:
>>
>>> I currently have some uncommitted changes on the bundlerepository 
>>> bundle, but I should commit them soon and then we will can go full 
>>> force into creating the new build process. So, we need some people 
>>> with good Maven know-how to get the ball rolling.
>>
>>
>> I can help get it started during the evenings this week.  Just let me 
>> know when you want to freeze the code.  I still need to flatten the 
>> tools directory, so I'll do that at the same time.
>>
>>> I had also thought that maybe we should set up a Felix "subproject 
>>> template" subproject so that new subprojects can simply copy it into 
>>> their directory...this might be helpful since we have a handful of 
>>> outstanding contributions that will hopefully get their paperwork 
>>> situations finalized soon.
>>
>>
>> I wonder if a maven archetype might help.
>
>
> Also note that we've learned some valuable lessons from trying to 
> follow the proposed maven layout when it comes to the artifactIds and 
> groupIds used over at Directory.  Like for example we should not be 
> using the fully qualified package name for both the groupId and the 
> artifactId.  For GID this works for AID this is a disaster.
>
> Flat however is generally a good idea.  I learned this the hard way.
> Laters,
> Alex
> 

Re: Maven for Felix

[Alex Karasulu <ao...@bellsouth.net>]

Timothy Bennett wrote:

> Richard S. Hall wrote:
>
>> I currently have some uncommitted changes on the bundlerepository 
>> bundle, but I should commit them soon and then we will can go full 
>> force into creating the new build process. So, we need some people 
>> with good Maven know-how to get the ball rolling.
>
>
> I can help get it started during the evenings this week.  Just let me 
> know when you want to freeze the code.  I still need to flatten the 
> tools directory, so I'll do that at the same time.
>
>> I had also thought that maybe we should set up a Felix "subproject 
>> template" subproject so that new subprojects can simply copy it into 
>> their directory...this might be helpful since we have a handful of 
>> outstanding contributions that will hopefully get their paperwork 
>> situations finalized soon.
>
>
> I wonder if a maven archetype might help.


Also note that we've learned some valuable lessons from trying to follow 
the proposed maven layout when it comes to the artifactIds and groupIds 
used over at Directory.  Like for example we should not be using the 
fully qualified package name for both the groupId and the artifactId.  
For GID this works for AID this is a disaster.

Flat however is generally a good idea.  I learned this the hard way. 

Laters,
Alex

Re: Maven for Felix

[Timothy Bennett <ti...@exterminator-x.com>]

Richard S. Hall wrote:

> I currently have some uncommitted changes on the bundlerepository 
> bundle, but I should commit them soon and then we will can go full 
> force into creating the new build process. So, we need some people 
> with good Maven know-how to get the ball rolling.

I can help get it started during the evenings this week.  Just let me 
know when you want to freeze the code.  I still need to flatten the 
tools directory, so I'll do that at the same time.

> I had also thought that maybe we should set up a Felix "subproject 
> template" subproject so that new subprojects can simply copy it into 
> their directory...this might be helpful since we have a handful of 
> outstanding contributions that will hopefully get their paperwork 
> situations finalized soon.

I wonder if a maven archetype might help.

-- timothy