Re: [pde-build-dev] Re: Integrating with an external build system (Ant,

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

I should have said "matching attributes"
not "matching rules".  Basically OSGi supports a series
of mechanisms you can use to refine the dependencies.  You can for
example say you want package foo, version [1.0,1.2.3) where the exporting
bundle is produced by IBM and has the color yellow.  On the exporter;s
side you can do things like say that if someone consumes foo and also consumes
bar they should get the same bar as you.

Jeff

"Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

06/14/2006 05:01 PM

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] Re: Integrating with an external build system        (Ant, Maven, etc.)

No, a dependency in a POM (currently) always refers to some kind of physical
artifact - usually a jar. 
Maven does support version matching - you can specify one or more intervals
of requiredversions that are (like [ 2.0,3.0) ) Is that the kind of OSGi
matching rules you are referring to ?

Tom

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

Can the POM <dependencies> section be used to express package level
dependencies?  and the OSGi matching rules and directives etc?

Jeff

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

06/12/2006 01:23 PM

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

To	pde-build-dev@xxxxxxxxxxx
cc
Subject	Re: [pde-build-dev] Re: Integrating with an external build system        (Ant, Maven, etc.)

Just to clarify there is nothing wrong with the pom as I understand it.
 But we would need a plugin to dynamically resolved dependencies against
repo artifacts.

On 6/11/06, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx
> wrote: 
Hi!

It's interesting how things fall together. :)

There was a long discussion last week about the same topic on the
pde-build-dev mailing linst, which IMHO seems more on-topic for this
then the equinox-dev list that is supposed for discussions about 
developing Equinox.

http://dev.eclipse.org/mhonarc/lists/pde-build-dev/msg00184.html

Niclas Hedhman wrote:
> Well, Maven2 itself is pretty useless for everything. It can't even
compile a 
> Java file. Everything is doen with Maven2 plugins, and it just happens
that
> there are Maven2 plugins for developing OSGi bundles.

AFAIK the answer in this thread was that the Maven2 POM is not as
pluggable yet. OSGi would need a plug-in that would resolve the
dependencies dynamically based on the manifests and the available bundles.

Cu, Gunnar

--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev


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


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