[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Good support for PDE in build systems anyone?

On Monday 05 June 2006 10:28, Jeff McAffer wrote:
> Peter Neubauer wrote on 06/04/2006 03:47:51 PM:

> > 1) Manifest file
> > - one could think of a Maven builder generating new manifest.mf on
> > the fly as you edit the relevant POM/other metadata, like source code
> > triggering changed import statements
>
> Sure.  Note that PDE does not have to do anything here.  It will pick up
> any changes made to the manifest by such a builder.

So, would making the Maven OSGi plugin generating the Manifest for PDE make 
any sense?? I mean that is pretty trivial...

Another interesting thing to note, would be that one could probably create a 
new life cycle phase in Maven when doing OSGi bundles, which just after the 
POM has been read, reads the MEAT-INF/Manifest.MF and parse it for classpath 
entries and what-else needed from there and adds it to the Maven model.
Such approach would somewhat let the Manifest be the master, but I guess it is 
somewhat fragile as Maven savvy people would never conceive that to be a 
master file.


Also, how does PDE know what classpath to use for "unit testing" vs normal 
runs?? I also suspect that the developer is responsible for knowing the 
transitive dependencies, e.g. hibernate.jar needs jta.jar (among others). How 
about projects within the PDE workspace? Does it figure out that Project C 
needs hibernate, therefor Project F that depends on Project C will need it 
too? And in that case, how would it know whether Project C only needs 
hibernate during testing, and therefor Project F should not include it in its 
classpath?
These are the main reasons why I like to stick with Maven as the primary tool.


Cheers
Niclas