[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-build-dev] Re: Integrating with an external build system (Ant, Maven, etc.)
|
How would you create this index ? 'All the bundles that are available' is quite a lot - if you're talking about all artifacts available in public and private repositories. Or would you restrict this to plugins you have available locally ?
If this index would exist, it would also be easier to create a manifest-to-pom mapper. Then you could skip writing the custom resolver for now (which looks like the hardest part since it requires modifications to the maven core) and just create some custom compiler and packaging plugin as a proof of concept.
One more thing: what would happen when more than one plugin provides a required package ? How does the current PDE build handle this situation ?
Tom
On 6/15/06,
Jeff McAffer <Jeff_McAffer@xxxxxxxxxx> wrote:
Great. So what I'm imagining here
is a Maven plugin that takes a pointer to a manifest and a pointer to some
index info (listing all the bundles that are available). The plugin
would then create and resolve a "state" based on the two inputs.
From that the state can be traversed to discover all the prereqs,
their ordering and the access rules needed for each. the plugin
would inject the dependencies and Maven would do its magic to ensure tha
those jars are indeed in the local repo. The plugin would also work
with a compiler plugin to setup the correct command line (ie. with access
rules) is passed in at compile time. Does this make sense?
So it seems like what we need is someone
to try this. We can provide such a resolver (would take a few days
to put together) and the code to do the state traversal (for ordering)
and access rule computation but we lack the Maven know-how to do the integration.
Volunteers?
Jeff
Hei
Jeff McAffer wrote:
>
> Can the POM <dependencies> section be used to express package
level
> dependencies? and the OSGi matching rules and directives etc?
Currently it's only references artifacts where an artifact is a JAR file.
Don't know about the matching rules, possibly you would write your own
resolver.
It could actually be possible (with some custom maven component
implementation) to add dependencies on a package and then use a special
resolver to resolve the package to a JAR file.
--
Trygve
_______________________________________________
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
