[alesj]

I've managed to work around the problem locally by download the vfs beta-6 tag
and installing it into my local repository, but this clearly isn't the correct solution. ;-)

Why is then MavenReleaseProcess 'cookbook' missing 'maven install/deploy' instructions?

And probably this 'local install' should be also mentioned as a feasible workaround - although mvn error msg already proposes it. ;-)

[adrian.brock]

"alesj" wrote:

I've managed to work around the problem locally by download the vfs beta-6 tag
and installing it into my local repository, but this clearly isn't the correct solution. ;-)

Why is then MavenReleaseProcess 'cookbook' missing 'maven install/deploy' instructions?

And probably this 'local install' should be also mentioned as a feasible workaround - although mvn error msg already proposes it. ;-)

mvn deploy is for the legacy jboss repository used by jboss-head
http://wiki.jboss.org/wiki/Wiki.jsp?page=JbossDeployMavenPlugin
here: http://repository.jboss.com/

mvn install is for local repository installation

mvn release is for our maven repository (which is used by the MC build)
here: http://repository.jboss.com/maven2/
see the link I posted before: http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess

[adrian.brock]

"alesj" wrote:

I've managed to work around the problem locally by download the vfs beta-6 tag
and installing it into my local repository, but this clearly isn't the correct solution. ;-)

Why is then MavenReleaseProcess 'cookbook' missing 'maven install/deploy' instructions?

And probably this 'local install' should be also mentioned as a feasible workaround - although mvn error msg already proposes it. ;-)

No. It's only a workaround if you want to build things from source.

You can't expect everybody to checkout and build all libraries from source
and then install them into a local repository (and repeat the process on every new version).
We need them in our maven repository as binaries.

[alesj]

see the link I posted before: http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess

"alesj" wrote:

Did you follow this checklist?
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess

By the book. :-)

So, what am I missing then?

[alesj]

No. It's only a workaround if you want to build things from source.

You can't expect everybody to checkout and build all libraries from source
and then install them into a local repository (and repeat the process on every new version).
We need them in our maven repository as binaries.

I agree.
But could/should be there. It's a wiki afterall. ;-)

Just in case people get stuck - which in case of maven and unskilled release devs :-) is very likely.

[adrian.brock]

"alesj" wrote:

So, what am I missing then?

A 2.0.0-beta6 here would be nice :-)
http://repository.jboss.com/maven2/org/jboss/jboss-vfs/

[alesj]

"alesj" wrote:

So, what am I missing then?

A 2.0.0-beta6 here would be nice :-)
http://repository.jboss.com/maven2/org/jboss/jboss-vfs/

No, that's what you are missing. :-)

I mean, how come this didn't get populated during my mvn-release cookbook procedure?
Missing some settings? Since I don't touch my mvn settings if not necessary. ;-)

[alesj]

"alesj" wrote:
I mean, how come this didn't get populated during my mvn-release cookbook procedure?
Missing some settings? Since I don't touch my mvn settings if not necessary. ;-)

Or does this last step - 'The deployment is done to the local file system (a local checkout of the jboss maven2 repository), so you will need to commit the new files after they are deployed.' - imply that you also have to commit all this generated artifacts to our mvn2 repo as well?

If so, then it should be noted that you have to commit it to both places - our maven2 repo location + old buildmagic pickup place.

[adrian.brock]

"alesj" wrote:

I mean, how come this didn't get populated during my mvn-release cookbook procedure?
Missing some settings? Since I don't touch my mvn settings if not necessary. ;-)

No idea, ask in the build forum. I can't even dryRun the release:prepare (see above)
so maybe you ignored/missed that error message?

[alesj]

I can't even dryRun the release:prepare (see above)
so maybe you ignored/missed that error message?

I had no problems running dry release.
That's the first time I saw your (see above) problem.

[pgier]

When I try to dryRun the release I get the following cryptic error message:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] You don't have a SNAPSHOT project in the reactor projects list.

The only thing I can find on the internet is a couple of bug reports that
don't explain what it means:
http://jira.codehaus.org/browse/MRELEASE-246
http://jira.codehaus.org/browse/MRELEASE-279

If you are using the release plugin, you should be releasing a project that is currently a snapshot. If the project is not a snapshot, then the release plugin complains that you are trying to release something that is already a release.

Just change the version in the pom to <release-version>-SNAPSHOT and it should be ok.

[pgier]

"alesj" wrote:

"alesj" wrote:
I mean, how come this didn't get populated during my mvn-release cookbook procedure?
Missing some settings? Since I don't touch my mvn settings if not necessary. ;-)

Or does this last step - 'The deployment is done to the local file system (a local checkout of the jboss maven2 repository), so you will need to commit the new files after they are deployed.' - imply that you also have to commit all this generated artifacts to our mvn2 repo as well?

If so, then it should be noted that you have to commit it to both places - our maven2 repo location + old buildmagic pickup place.

The release plugin does a maven deploy at the end of the "mvn release:perform" step. This will copy the poms and jars to the directory that you specify and generate the checksum files and metadata. Since we use an svn repository for our maven repo, you then need to check in the project files, checksums, and metadata.

So yes, you have to svn commit both to the maven repo and to the jboss repo if you want the jars available in both places.

Feel free to update the wiki if the explanation is not clear ;)

[alesj]

"pgier" wrote:

So yes, you have to svn commit both to the maven repo and to the jboss repo if you want the jars available in both places.

Commited to maven2 repo as well:
- http://repository.jboss.com/maven2/org/jboss/jboss-vfs/2.0.0.Beta6/