You are viewing a plain text version of this content. The canonical link for it is here.

Posted to npanday-commits@incubator.apache.org by "Brett Porter (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/21 03:44:43 UTC

[jira] [Resolved] (NPANDAY-168) Generating a POM for a solution that already has them should use defaults from the current POM

     [ https://issues.apache.org/jira/browse/NPANDAY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter resolved NPANDAY-168.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Backlog)
                   1.5.0-incubating
         Assignee: Brett Porter

Was already the case for SCM and version, added for groupID
                
> Generating a POM for a solution that already has them should use defaults from the current POM
> ----------------------------------------------------------------------------------------------
>
>                 Key: NPANDAY-168
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-168
>             Project: NPanday
>          Issue Type: Bug
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.5.0-incubating
>
>
> The dialog returns to the defaults from the original request (eg. CompanyName.SolutionName for the group ID). It should instead re-use anything it can load from the solution root POM if it already exists.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira