You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2007/09/15 06:34:11 UTC

[jira] Updated: (CONTINUUM-1435) Release prepare not working

     [ http://jira.codehaus.org/browse/CONTINUUM-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak updated CONTINUUM-1435:
-----------------------------------

         Priority: Blocker  (was: Major)
    Fix Version/s: 1.1-beta-3

Confirmed not working in r575816.  Upgrading to blocking issue for the next release.

> Release prepare not working
> ---------------------------
>
>                 Key: CONTINUUM-1435
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1435
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-2
>         Environment: Java 5 Update 12
> Maven 2.0.4
>            Reporter: Dário Oliveros
>            Priority: Blocker
>             Fix For: 1.1-beta-3
>
>         Attachments: continuum-release-patch.txt, continuum-webapp-patch.txt
>
>
> The following error occurs when trying to prepare a release of a project:  
>   java.io.FileNotFoundException: 1/pom.xml (No such file or directory)
> Note: It used to work on 1.1-beta-1 version.
> I noticed that the WORKING_DIRECTORY column of the PROJECT table does not contain the absolute path anymore. So when invoking the project.getWorkingDirectory() method on ReleasePrepareAction class  you will get as result the relative path only.
> This bug can be reproduced by doing a fresh install, adding a new Maven 2 project and preparing its release. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira