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 "Joe Ocaba (JIRA)" <ji...@apache.org> on 2010/12/07 05:51:09 UTC

[jira] Resolved: (NPANDAY-69) NPanday needs to be more synchronized and automated

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

Joe Ocaba resolved NPANDAY-69.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Backlog)
                   1.3-incubating
         Assignee: Joe Ocaba

Fix with NPANDAY-157, NPANDAY-212, NPANDAY-178

> NPanday needs to be more synchronized and automated
> ---------------------------------------------------
>
>                 Key: NPANDAY-69
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-69
>             Project: NPanday
>          Issue Type: Bug
>            Reporter: Joe Ocaba
>            Assignee: Joe Ocaba
>            Priority: Minor
>             Fix For: 1.3-incubating
>
>
> Each time there is a new addition like a resx or other sources to the project, it will not be reflected towards the pom and if you would do a re import the needed tags like scm and the version of the parent tags.
> Our final goal would be to have npanday running on the background. All the user has to do is import the project and if the user has any modifications done in VS then it should be reflected in the pom. At the moment this is only applicable with references.
> If ever we also need to re import then tags like scm, parents and other important tags should be preserved.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.