Hi,
the maven-release-plugins only accepts ${project.version} for
reactor-projects, i.e. projects being part of a multi-module project.
The fact that your projects are separated also means that they both have
their own release-cycle. As you describe, they often(!) will be the same,
but if your MSI config is changed, does that require a new project-main?
So I understand why it was implemented like this.
You could change the value for allowTimestampedSnapshots[1] to true, but
then you've lost the check for all snapshots.
What you could probably do is combine this with the enforcer rule called
RequireReleaseDependencies[2] (have never done this myself though).
Robert
[1]
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#allowTimestampedSnapshots
[2] http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
Op Thu, 13 Dec 2012 13:51:06 +0100 schreef Dan Godfrey
<[email protected]>:
Hi,
I'm having trouble using the release-plugin on a project as it is
complaining that it has snapshot dependencies, even though those
dependencies are actually set to ${project.version}. So when the
dependency
check phase runs they are indeed SNAPSHOT dependencies, if it were to
continue then they would be updated to non-SNAPSHOT dependencies in a
later
phase.
I was wondering if anybody knows of anyway to get around this?
To explain why: I have 2 separate projects project-main &
project-windows.
project-main is a jar (well multiple jars)which are deployed to our local
repo. project-windows then takes that deployed jar and packages it up as
an
MSI. Both of these projects are kept in lockstep with regards version
numbers and have separate CI jobs. I've split the 2 projects up in
different SCM repos like this as we have have other CI jobs depending on
project-main for testing, and potentially in the future a project-linux,
etc.
Thanks,
Dan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
