Share

December 12, 2008

Maven 2 - Couldn't find the release X among the supplied releases

In my Blog about maven-changes-plugin. I made the following comment


Note: The changes plugin has an issue where if the changes.xmldoes not include an entry for a release matching the build releaseversion, the build will fail after deploying the war/jar/etc to themaven repository.
Here is an example of that error...

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Couldn't find the release '1.14.2' among the supplied releases.
[INFO] ------------------------------------------------------------------------

Again the fix is to make sure that the changes.xml has a release with the same number that you are building... and to fix that after the maven has tagged your source code is to check in an updatedchanges.xml with a matching release and retag it with the release tagthen call cvs update and mvn release:prepare again

3 comments:

  1. i changed my change.xml still the same problem.
    [INFO] Reactor build order:
    [INFO] GDC
    [INFO] GDC Core
    [INFO] GDC Tools Core
    [INFO] GDC Tools Data
    [INFO] GDC Droplets
    [INFO] GDC Tools Droplets
    [INFO] Searching repository for plugin with prefix: 'changes'.
    [INFO] ------------------------------------------------------------------------
    [INFO] Building GDC
    [INFO] task-segment: [changes:announcement-check, clean, install]
    [INFO] ------------------------------------------------------------------------
    [INFO] [changes:announcement-check]
    [INFO] artifact com.mtvi.plateng.maven:maven-utils-plugin: checking for updates from mtvn-proximity
    [INFO] [clean:clean]
    [INFO] Deleting directory /u/wc/workspace/Mine/gdc_test/target
    [INFO] [enforcer:enforce {execution: enforce-versions}]
    [INFO] [site:attach-descriptor]
    [INFO] Unable to load parent project from a relative path: Could not find the model file '/u/wc/workspace/Mine/pom.xml'. for project unknown
    [INFO] Parent project loaded from repository.
    [INFO] Preparing source:jar
    [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
    [INFO] [enforcer:enforce {execution: enforce-versions}]
    [INFO] [source:jar {execution: attach-sources}]
    [INFO] [install:install]
    [INFO] Installing /u/wc/workspace/Mine/gdc_test/pom.xml to /home/kumaras/.m2/repository/com/mtvnet/gdc/gdc/1.3/gdc-1.3.pom
    [INFO] ------------------------------------------------------------------------
    [INFO] Building GDC Core
    [INFO] task-segment: [changes:announcement-check, clean, install]
    [INFO] ------------------------------------------------------------------------
    [INFO] [changes:announcement-check]
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Couldn't find the release '1.3' among the supplied releases.
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 1 minute 25 seconds
    [INFO] Finished at: Wed Jul 08 03:39:28 EDT 2009
    [INFO] Final Memory: 43M/509M
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------

    ReplyDelete
  2. You have to make sure that the change.xml has been retaged (moved tag ) with 1.3 so that when maven rechecks out files it get the new updated one.

    ReplyDelete