[
http://jira.codehaus.org/browse/CONTINUUM-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed CONTINUUM-1435.
---------------------------------------
Assignee: Emmanuel Venisse (was: Olivier Lamy)
Resolution: Fixed
Fixed.
I applied this match with few modifications because it introduced a cycle in
dependencies between continuum-core and continuum-release so I move some
classes from continuum-core to continuum-commons and removed the cycle.
Thanks Dario
> 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
> Assignee: Emmanuel Venisse
> 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
