Re: [pde-build-dev] Eclipse Builds and Maven 2.x

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

As I understand Peter's code, it *generates*
Import-Packages etc in the generated manifest during a Maven build.  This
information is not used while doing the dependency analysis and classpath
modelling.  AFAIK, that is still managed/directed by the info in the
POM.  It seems that it hsould be possible to read the manifest and
then call methods on the object model to add the defined dependencies.
 However the dependencies are still at the wrong granularity (whole
bundle/jar level) for real OSGi work.

Jeff

"Wendell Beckwith" <wbeckwith@xxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

06/07/2006 09:21 AM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	Re: [pde-build-dev] Eclipse Builds and Maven 2.x

On 6/7/06, Wendell Beckwith <wbeckwith@xxxxxxxxx>
wrote:


On 6/6/06, Jeff McAffer <
Jeff_McAffer@xxxxxxxxxx> wrote:

Wendell Beckwith wrote on 06/06/2006 07:41:39 PM:


> This came up previously in this thread, http://dev.eclipse.
> org/mhonarc/lists/pde-build-dev/msg00076.html, but it seems to have
> fallen on the floor and rolled under the couch.  Nonetheless,
my 

Every once in a while we get a stick and poke around in the dark recesses
under the couch but mostly this topic seems to just roll further away...
 :-) 

Seriously, it is quite interesting.  There is no desire to lock people
into PDE or have PDE rule the world.  The main barrier has been the
work required for us to get to know Maven and others getting to know PDE
Build...  While the approach you outline feels plausible, there are
some fundamental technology issues that need to be understood and addressed.

- Dependency management : Maven has a reasonable mechanism for finding
and resolving dependencies.  Unfortunately, the OSGi dependency model
is considerably richer.  As a result, maven will not know, for example,
how to deal with Import-Package statements that spec arbitrary dependencies
and use the "uses" directive.

I don't know it everyone  is aware of this but Peter  Kriens
 from OSGi  has written and donated code to the Apache Felix
project which seems to do what you are talking about.  Check out the
April 24 blog entry here, http://www.osgi.org/blog/2006_04_01_archive.html.
 I haven't looked at the code yet, but I remembered reading this a
while ago and didn't have time to follow up until now. 

[snip]

Wb_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev