> Having them in the repo enables sharing them between the team, and I
> can imagine that at some point we'll be able to build and test without
> the installation but as jetty:run does with J2EE.
Who on the team is not going to have Eclipse installed? Even on a
build server you would just install Eclipse. Not doing that means
you're going to end up with a GB of duplication if you're using/
testing with multiple versions of Eclipse.
The Maven repository is in a known location for Maven.
However the Eclipse installation will require some non-pom
configuration details to be provided. (I agree that it is likely to be
installed on all machines)
It would also require verification that the installation specified is
the version required. (i.e. pom defines version 3.2.2 but local
installation is 3.1.0)
All of these issue can be resolved, it would be nice if it could be
done in a consistent way.
At the moment I have used the maven-eclipse-plugin to duplicate the
Eclipse installation into the repository. The benefit of this is the
ability to create Eclipse Target Platforms using transitive
dependencies.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
