incubator-nmaven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (NMAVEN-151) Solution file should include the pom so that it can be edited in Visual Studio
Date Sun, 13 Jul 2008 14:49:26 GMT

     [ http://jira.codehaus.org/browse/NMAVEN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wendy Smoak closed NMAVEN-151.
------------------------------

         Assignee: Wendy Smoak
       Resolution: Won't Fix
    Fix Version/s:     (was: 0.14 (Unreleased))

After more thought, I don't actually want this. :)  The real problem is incomplete integration
with the Visual Studio UI.  Developers shouldn't have to edit the pom.xml file any more than
they edit the .sln or .csproj files.



> Solution file should include the pom so that it can be edited in Visual Studio
> ------------------------------------------------------------------------------
>
>                 Key: NMAVEN-151
>                 URL: http://jira.codehaus.org/browse/NMAVEN-151
>             Project: NMaven
>          Issue Type: Improvement
>    Affects Versions: 0.14 (Unreleased)
>         Environment: NMaven 0.14 branch + patches
>            Reporter: Wendy Smoak
>            Assignee: Wendy Smoak
>            Priority: Minor
>
> When generating solution files or importing projects (generating poms), the pom.xml file(s)
should be added to the solution so that they appear in the Visual Studio solution editor and
can be opened within the IDE.
> Workaround:  right-click on project, Add -> Existing Item -> change to *.xml and
choose pom.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message