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 computation of the classpath takes as input a state that has the fully resolved dependencies.  So the prerequisite is that the dependency resolution is done.

We have a work item to refactor out the resolver into a standalone jar (https://bugs.eclipse.org/bugs/show_bug.cgi?id=148121), this may take a while, in the mean time we can just use the org.eclipse.osgi bundle as a whole which is just a superset of what we need.

The classpath calculation is currently done by org.eclipse.pde.build/org.eclipse.pde.internal.build.builder/ClasspathComputer3_0.  

Over the next couple of days I'll put together a bundle for you guys that will use the resolver and classpath computer to set up the classpath and access rules.  Whether or not I can hack the resolver out of the osgi bundle is not so important right now.
We will also want something that can put together a list of manifest file locations out of the repo for input to the resolver.

-Andrew



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

06/22/2006 11:59 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.)





I was under the impression that we were trying this out and that we were waiting on the PDE team to provide the code.  Would it be more appropriate at this time to open an issue or join an issue already open to track progress?

I've recently been moved to a position that will allow me more time to focus on this.  Personally I'd like to get everything working before the summer is over.  Whether PDE switches to it or not is a different story, but if done right there should be no impedance to doing so.

Wb

On 6/22/06, Tom Huybrechts <tom.huybrechts@xxxxxxxxx> wrote:
I'd like to try this out, starting with the compile part - the easiest I think. Suppose I have a manifest and a list of jars that are the prereqs (I'll just put these as dependencies in the pom for now). How do I turn this into a classpath (and any other args) that can be passed to the compiler ?

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




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


Back to the top