[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-build-dev] Eclipse Builds and Maven 2.x
|
I understood that your scenario was a "what-if". What I wanted to be clear on was that I was not proposing to change your build system (ant) from what it is today to my build system (maven). Personally I didn't think it was up for discussion. Nonetheless, from Pascal's previous email it looks like pde would be interested in exploring whether the grass is greener on the other side. If that is indeed the case, then I'm willing and able to investigate how this could be done with maven. One point I have is how far does pde want, or is willing, to go with maven, minimal disruption for some x amount of benefit or full bore balls to the walls maven or die trying for x+y benefit?
Wb
On 6/7/06, Jeff McAffer <Jeff_McAffer@xxxxxxxxxx> wrote:
Wendell Beckwith wrote on 06/07/2006 02:08:06 AM:
> Wendell Beckwith wrote on 06/06/2006 07:41:39
PM:
> It would be extremely interesting to see how
one could use Maven to
> build, for example, the RCP feature for several platforms (say Win32
> and Linux GTK x86) and produce the corresponding zips. By this
I
> mean, ignore PDE Build and imagine that we all went native Maven,
> fell in love with POMs and all started hand crafting them every
> chance we had. What would the POMs look like? How would
it work?
> Would it work? How are the points above addressed? Having
> understood this we can then look at how to automate parts of that
process.
>
> Does that make sense?
>
> Yes, it makes sense, but if you all went native and became card
> carrying mavenites then I would likely have my problems solved but
> others would still be in the same boat. After I sent my original
My scenario was a "what-if". The
point is that we have to prove that it is even possible to use Maven to
build what we need to build. If it is not then much of the discussion
is moot.
> email I started thinking that what was needed
was not a simple build
> script, but instead a build model. If we can describe and declare
> how a feature/plugin build model should work then we can then
> explore how to map that model to ant, and maven. With ant and
maven
> providing concrete implementations of the build model, other parties
> could plugin in their own models. In my mind the build model
should
> support using all of say maven for the entire build as well as using
> an IAntScript to fetch the source, eclipse to compile and test it
> and finally maven to assembly, package and deploy it.
>
> Now does what I said make sense to you?
Yes except that we don't really want to grow PDE Build
to be some uber build mechanism that orchestrates other builds. Making
the build system pluggable (as in replacing the guts with Ant, Maven, ...)
is interesting but in the end we are more interested in extensibility (as
in adding more capabilities). I don't think we are at odds here,
more like a different point of view.
In any event, are you able/willing to do some investigation
into hand rolling a build of say the RCP feature as described earlier?
Jeff
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
