Hi,
On Thu, Oct 22, 2009 at 2:27 PM, Sean Owen <[email protected]> wrote:
> Are we supposed to run from the parent module, or root level? which
> pom.xml should operate the build?
The root level.
> I'm definitely seeing errors about ${project.version} not being
The INFO messages about "Ignoring artifact version update for
expression: ${project.version}" are expected. In a multimodule build
the release plugin will automatically update the versions of
dependencies that are included in the same build. If such a dependency
is already declared as having version ${project.version}, then there's
no need for the release plugin to explicitly change that setting. The
info message is just printed to highlight this point.
> What is '-Papache-release' -- I'm trying to figure out whether this is
> supposed to be set or not. Some people mentioned this, not seeing it
> in docs.
That comes from the release profile settings in the latest
org.apache:apache parent POM that Mahout is now using. See
http://repo2.maven.org/maven2/org/apache/apache/6/apache-6.pom for the
full details.
> I don't see that we have any instance of maven-release-plugin -- should we?
Things like the release plugin settings mentioned by Benson earlier
are already configured in that parent POM, so unless you explicitly
want to override things, there's no need to have such settings in
Mahout.
> I have Subversion 1.6.2 FWIW.
About the svn problems you were seeing earlier: Are you located in
Europe? The sync delay of the local svn.apache.org mirror causes such
problems every now and then. Luckily the release plugin can fairly
well deal with such problems. Simply rerun "mvn release:prepare" a bit
later, possible with an "svn update" in between, to continue the
process.
BR,
Jukka Zitting
