that release. Agile
states that your software should be releasable at anytime, but it does not
state that it should be continually released.
Of course, the opposite (ie: not releasing enough) is just as bad if not worse.
Have to find that sweet spot ;-).
---
Todd Thiessen
-Original Message
.
These are alphas and getting them out as soon as the rules
allow here
is important for people trying to evaluate 3.x.
---
Todd Thiessen
-Original Message-
From: paulus.benedic...@gmail.com
[mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict
Sent: Wednesday
The m2e plugin I think already does what you are looking for. It has a
dependency heirarchy and graph. I use these often to determine what
libraries are being used when there is a conflict.
---
Todd Thiessen
-Original Message-
From: Setter Guo [mailto:setter@yahoo.com]
Sent
the maven-scm submodule projects as
dependancies by explicitly specifying their version. How are the version
numbers of all these dependencies incremented when a new version of the
plugin is released?
---
Todd Thiessen
Thanks Mark. I will do that.
---
Todd Thiessen
-Original Message-
From: Mark Struberg [mailto:strub...@yahoo.de]
Sent: Monday, January 19, 2009 9:37 AM
To: scm-dev@maven.apache.org
Subject: RE: SCM plugin project
Open a Jira, ship the patch, and I bet you'll get response
in the SCM project but of course affects the change log
plugin. Thus I raised a jira for both.
Please comment/vote etc...
Thanks.
---
Todd Thiessen
