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 (JIRA)" <ji...@apache.org> on 2011/06/15 07:37:47 UTC
[jira] [Created] (NPANDAY-444) Duplicate dependency being added
while re-generating the POM file
Duplicate dependency being added while re-generating the POM file
-----------------------------------------------------------------
Key: NPANDAY-444
URL: https://issues.apache.org/jira/browse/NPANDAY-444
Project: NPanday
Issue Type: Improvement
Components: Visual Studio Add-in
Affects Versions: 1.4-incubating
Reporter: Brett Porter
Currently, if you regenerate the POM file with a different Group ID, the previous dependencies within the project are not renamed, but instead retained and re-added with the new group ID.
It would make more sense if the "generate" was treated like a "sync" task that updates any discrepancies, and if the group ID is different to last time then the other dependencies are rewritten instead of being additive.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-444) Duplicate dependency being added
while re-generating the POM file
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated NPANDAY-444:
---------------------------------
Fix Version/s: Backlog
> Duplicate dependency being added while re-generating the POM file
> -----------------------------------------------------------------
>
> Key: NPANDAY-444
> URL: https://issues.apache.org/jira/browse/NPANDAY-444
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Affects Versions: 1.4-incubating
> Reporter: Brett Porter
> Fix For: Backlog
>
>
> Currently, if you regenerate the POM file with a different Group ID, the previous dependencies within the project are not renamed, but instead retained and re-added with the new group ID.
> It would make more sense if the "generate" was treated like a "sync" task that updates any discrepancies, and if the group ID is different to last time then the other dependencies are rewritten instead of being additive.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira