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

[jira] Closed: (CONTINUUM-1219) Error releasing projects with deep nested parent-child relationship between itself and some of it's modules

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

Emmanuel Venisse closed CONTINUUM-1219.
---------------------------------------

         Assignee: Emmanuel Venisse  (was: Lester Ecarma)
       Resolution: Fixed
    Fix Version/s: 1.1-alpha-1

Applied.

> Error releasing projects with deep nested parent-child relationship between itself and some of it's modules
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1219
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1219
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.0.3
>            Reporter: Lester Ecarma
>         Assigned To: Emmanuel Venisse
>             Fix For: 1.1-alpha-1
>
>         Attachments: continuum-1219.patch
>
>
> Error occurs in the prepare release step.
> To replicate, try to release the maven project and you will get this error:
> [INFO] Updating local copy against the scm...
> [INFO] Verifying that there are no local modifications...
> [ERROR] org.apache.maven.shared.release.ReleaseFailureException: Can't release project due to non released dependencies :
> org.apache.maven.reporting:maven-reporting-api:jar:2.0.5-maestro-1.2-SNAPSHOT:compile
> in project 'Maven Core' (org.apache.maven:maven-core:jar:2.0.5-maestro-1.2-SNAPSHOT)
> at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkProject(CheckDependencySnapshotsPhase.java:225)
> at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.execute(CheckDependencySnapshotsPhase.java:101)
> at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:205)
> at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:118)
> at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:43)
> at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
> at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
> at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
> at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:619)

-- 
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