[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-build-dev] Eclipse Builds and Maven 2.x
|
Currently the whole dependency resolution thing is not pluggable IIRC. However, Brett previously stated that it could be made pluggable. If that is done then the default implementation of this IMavenDependencyResolver would work for maven backwards compatibility and an alternate could be selected via properties and/or command line for eclipse/osgi builds.
Now that we seem to have a meeting of the minds where is the best place to start? I have started reading the build automation article, but I'm not done yet. Also I have seen comments of multiple platforms/operating systems, but are there other variables we need to be concerned with such as defect tracking systems, cm systems, build servers like anthill pro, continuum, ...?
Wb
P.S.
Are you all aware that you can take an ant script and expose it as a maven plugin? Maven will then invoke the appropriate ant targets under the covers. Maven users are exposed to this and really should care whether the maven plugin they're using is ant-based or java-based unless performance or memory becomes an issue.
On 6/7/06, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> wrote:
I think I start to see your points about
integration but I'm a bit surprised as I thought that the whole dependency
resolution was not pluggable.
>Does PDE care
that the source was fetched with ant and place at /x/y/z or does it merely
want the action performed?
PDE does not care how the source is
obtained, in the end it just needs to know where on the local filesystem
it is located and what to do with it (this is why we have the build.properties).
PaScaL, curious to taste the maven kool-aid.
