Kurt Zettel created MRELEASE-781:
------------------------------------
Summary: Plugin allows releases which use the LATEST keyword on a
pom import
Key: MRELEASE-781
URL: https://jira.codehaus.org/browse/MRELEASE-781
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.3.2
Reporter: Kurt Zettel
I have several shared core projects that are released and built together:
core
\-core-utils-1
\-core-utils-2
I then have many projects that use core and they may or may not be released
with core so I have them point to "LATEST". This allows CI to keep all of
these projects always pointing to the latest.
I do this using a pom import of the core's pom in the dependency management
section.
{code:xml}
<?xml version="1.0" encoding="ISO-8859-1"?>
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
...
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.example</groupId>
<artifactId>core</artifactId>
<version>LATEST</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
...
</project>
{code}
I can then import whatever specific core projects I need and ignore the ones I
don't in the actual dependency section.
The problem is that if I release the project it doesn't fail if LATEST is
resolved to a tagged version. It resolves it and doesn't actually update the
pom.
What I would expect is for it to fail because LATEST isn't a specific version
and the build isn't reproducible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
