"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.
"scott.stark(a)jboss.org" wrote :
| 2. The eclipse project classpath settings need to be updated for the version updates
as part of the release process.
|
Would it be better to not have the .project and .classpath in subversion? I normally use
the IDE plugin (
http://m2eclipse.codehaus.org/) and it generates the classpath for me from
the pom. It's not perfect, but it's gradually getting better.
Also, don't some people use IDEA? The .project and .classpath are useless for them
anyway.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082276#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...