Skip to main content

[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.)


The MRM is not released yet, and questions about its status are usually ignored on maven-users.
I believe MRM creates an index using Lucene, that contains some standard metadata information from the poms and class and package names for jars. It could probably be extended to also index manifest information (like Bundle-SymbolicName, or Export-Package).

Tom


On 6/15/06, Andrew Niefer <aniefer@xxxxxxxxxx> wrote:

There does seem to be a Maven Repository Manager (http://jira.codehaus.org/browse/MRM) which builds an index of the repo.  Though I'm not sure what the state of this is.

Ideally we would want this index to contain manifest information.  If this index contained the appropriate information, we wouldn't need a standard mapping from Bundle-SymbolicName to groupId/artifactId since the index would have the information required to figure that out.


-Andrew


Jeff McAffer/Ottawa/IBM@IBMCA

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








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



Trygve Laugstøl <trygvis@xxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

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









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


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




Back to the top