You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Struberg (JIRA)" <ji...@codehaus.org> on 2011/06/12 18:07:42 UTC
[jira] Closed: (MRELEASE-683) maven:perform will not release
projects unless the pom file is in the top directory in the SCM repo
[ http://jira.codehaus.org/browse/MRELEASE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg closed MRELEASE-683.
----------------------------------
Resolution: Duplicate
Fix Version/s: 2.2
Assignee: Mark Struberg
this is a duplicate of MRELEASE-457 which is already implemented in release 2.2
> maven:perform will not release projects unless the pom file is in the top directory in the SCM repo
> ---------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-683
> URL: http://jira.codehaus.org/browse/MRELEASE-683
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.1
> Environment: linux/mac
> Reporter: Lee Thompson
> Assignee: Mark Struberg
> Fix For: 2.2
>
>
> Playing around with the MOJO project hosted in GIT.
> I can't release a plugin unless all the MOJO projects are split into their own GIT repos. If you want to put all plugins in one GIT repo, checkout the code, jump into a plugin project and release just that one plugin... release:perform will not jump into the right sub-directory of the GIT repository.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira