"scott.stark(a)jboss.org" wrote : "pgier" wrote :
"scott.stark(a)jboss.org" wrote :
| | | 1. Being able to to a mvn release:* to create the canonical maven2 artifacts
as well as the jboss repo artifacts. A current issue is how the versioning is handled. You
have to have x.y-SNAPSHOT releases of every project, and these are updated to
x.(y+1)-SNAPSHOT in trunk (unless overriden). This does not match our versioning
conventions of x.y.z.[Alpha|Beta|CR|GA] in that there can be several x.y.z releases with
only the qualifier changing. Its a pain to have to override the release and next version
for a large project like javaee, and worse for the mc. Can we customize this to better
match our conventions?
| | |
| | We don't have many options for customizing the defaults for a release. For
example, the release plugin doesn't have any way to know whether the next release
after Beta1 should be Beta2 or CR1. For mc I don't think it's an issue because
all the modules have the same version, so you just have to type it in once. With javaee
since all the sub-projects are at different versions, there isn't any way I can think
of to get around just entering the version for each one.
| |
| We need to start working towards such a feature request then. This is a simple plugin
enhancement to obtain the next version, and the plugin can request what info it needs to
determine if the release is moving from Beta1 to Beta2 vs Beta1 to CR1 or GA.
|
The release plugin already prompts you for the release version, tag, and next version.
What is the enhancement that you are looking for?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082294#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...