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 "Lars Corneliussen (JIRA)" <ji...@apache.org> on 2011/05/02 10:51:03 UTC

[jira] [Created] (NPANDAY-423) Also regenerate npanday-settings.xml on new NPanday-version

Also regenerate npanday-settings.xml on new NPanday-version
-----------------------------------------------------------

                 Key: NPANDAY-423
                 URL: https://issues.apache.org/jira/browse/NPANDAY-423
             Project: NPanday
          Issue Type: Improvement
          Components: Development Setup
            Reporter: Lars Corneliussen


Now we only regenerate, if the frameworkVersion does not exist in npanday-settings.xml

But, if we add new features (that require additions in npanday-settings.xml), those would come in a new NPanday version and it would be a good point where to delete the settings.

Also when running multiple npanday-plugin-versions separately we could ensure that the settings are regenerated on each version change.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (NPANDAY-423) Also regenerate npanday-settings.xml on new NPanday-version

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/NPANDAY-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated NPANDAY-423:
---------------------------------

    Fix Version/s: Backlog

> Also regenerate npanday-settings.xml on new NPanday-version
> -----------------------------------------------------------
>
>                 Key: NPANDAY-423
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-423
>             Project: NPanday
>          Issue Type: Improvement
>          Components: Development Setup
>            Reporter: Lars Corneliussen
>             Fix For: Backlog
>
>
> Now we only regenerate, if the frameworkVersion does not exist in npanday-settings.xml
> But, if we add new features (that require additions in npanday-settings.xml), those would come in a new NPanday version and it would be a good point where to delete the settings.
> Also when running multiple npanday-plugin-versions separately we could ensure that the settings are regenerated on each version change.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira