Re: [Aperture-devel] Further Mavenization & OSGi

[Herko t. H. <her...@ad...>]

Leo Sauermann wrote:

> Hi, I agree, with important comments:

>> Added goals are:
>> - the ability to build plain jars as well as OSGi-compatible jars
>>   
> no, in my view this can read:
> - the ability to build plain jars that are also OSGi compatible jars (= 
> we have one JAR release that is both plain jar and OSGi)
> This is easily possible without maven, you just tweak (by hand) the 
> manifest, and gotcha.
> with maven, I guess you have suddnely a dependency on OSGi in the artifact,
> which may cause an import-cascade to the full osgi frenzy for the 
> plain-java users.
> if this is the case, then it reads as you said

Right, fully agree. We'll just have the one jar for each module that 
contains an OSGi-compatible manifest and possibly an Activator that 
plain-jar users can safely ignore. There will be no dependency on OSGi 
for plain-jar users.

> imho we also have to add this:
> - the ability to build two plain jars (core, impl) for easy-going 
> developers
> - the ability to build two osgi jars (core, impl) for easy-going 
> developers (such as NEPOMUK)

Ok.


>> With the added effort made by Antoni and Gunnar to get the previously 
>> unreleased dependencies either releaseable or removed, I feel 
>> confident I can get it done this time.
>>   
> 
> good, this is very positive news!
> 
> I would think it would be good to have all changes done within a month,
> so that your branch does not get too far away from trunk

Actually, I'm going to try to get most of it done by the end of next 
week :) I should be able to at least get it working well enough so 
further development can take place in the Mavenized version (meaning the 
full project can be built with Maven).

Cheers,

Herko