I have commented on 207, I will have a look at a patch for the base
pom to add plugin dependencies and check that a release would work
tomorrow (if no one else gets there first)
Ian
On 22 Apr 2008, at 18:49, Brian Eaton wrote:
On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <[EMAIL PROTECTED]> wrote:
Dependencies,
We should have a dependency management statement in the base pom
that
contains the version numbers of everything we use (except internal
references) so that we dont have to remember or update version
numbers.
I think I figured out how to do this, patch attached:
https://issues.apache.org/jira/browse/SHINDIG-207
I also documented how I got Eclipse and maven to play nicely together.
mvn eclipse:eclipse has never worked for me, so somebody else will
have to document how that works.
We might also consider putting all the standard plugin config and
repo
information in the base pom.
This sounds like a great idea.
SNAPSHOT
the maven-release-plugin automates the tagging, version change,
release
process and deployment to the external maven repo.
Not editing required
This also sounds like a great idea.
