Well, we talked about all the possibilities of doing a PDE build with a 
consultant (who uses Tycho btw) and then decided that the best approach for us 
was just to treat the PDE build as black box and build a thin Maven layer 
around the whole build.
We're using m2eclipse, though (for non-PDE projects). 

> -----Ursprüngliche Nachricht-----
> Von: Brian E. Fox [mailto:[email protected]] 
> Gesendet: Donnerstag, 8. Januar 2009 17:23
> An: Maven Users List
> Betreff: RE: Dynamic dependencies?
> 
> Have you looked at Tycho and M2eclipse?
> 
> -----Original Message-----
> From: Lewis, Eric [mailto:[email protected]] 
> Sent: Thursday, January 08, 2009 8:00 AM
> To: Maven Users List
> Subject: AW: Dynamic dependencies?
> 
> Hello, anyone?  :-) 
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Lewis, Eric 
> > Gesendet: Dienstag, 30. Dezember 2008 16:18
> > An: 'Maven Users List'
> > Betreff: Dynamic dependencies?
> > 
> > Hi
> > 
> > I have a bit of a special problem. I want to use a Maven 
> > wrapper around an existing Eclipse PDE build, and this must 
> > be again deployed as Webstart application.
> > 
> > Now, I can call the PDE build, and it builds its stuff under 
> > target/deploy/${project.artifactId}-${project.version}-${times
> > tamp}/, and this directory has two subdirectories: features 
> > and plugins, which contains a lot of built JARs.
> > I've used the Webstart plugin before, and it handles declared 
> > dependencies well. However, I need to keep the 
> > features/plugins structure (if possible), and I need to 
> > unsign all JARs and then resign them with my key.
> > This would work if all the JARs were declared as dependencies 
> > in my POM (system dependencies, since they're not in my 
> > repository), but first of all, the PDE build is a black box 
> > from my build's point of view, and second the Eclipse 
> > developers don't want to synchronize all dependencies in 
> > Maven and PDE.
> > 
> > So, I think I need something that builds a dynamic 
> > dependencies list from several existing JARs. I guess that's 
> > the only solution, but perhaps someone has a better idea?
> > Anyway, is there a plugin that solves my problem? It would 
> > basically read a couple of directories and define all JARs in 
> > there as system dependencies.
> > 
> > Best regards,
> > Eric
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to