That's right... really, the circumstances for needing RELEASE are
diminishing, being mostly for plugins with unspecified versions, and
it is better to use the <versions> list instead.
- Brett
On 26/09/2008, at 8:06 PM, Benjamin Bentmann wrote:
Hi,
imagine an artifact that has currently two active development
branches, say one branch at version 2.x and the other branch at
version 3.x, both branches use the same groupId/artifactId for the
artifact.
Now, if a release is performed on the 3.x branch, the repo metadata
will be updated to have <release>3.x</release>. If later on a
release from the 2.x branch is performed, the repo metadata will
again be updated to have <release>2.x</release>, i.e. the release
info for the artifact is downgraded.
This looks odd. Merely depending on the timing of the releases, one
has either the 2.x artifact or the 3.x artifact as being "release".
Is that intentional?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
