You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jan ancajas (JIRA)" <ji...@codehaus.org> on 2008/04/09 11:23:58 UTC

[jira] Created: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Ability to generate pom.xml file from an existing Visual Studio solution file
-----------------------------------------------------------------------------

                 Key: NMAVEN-119
                 URL: http://jira.codehaus.org/browse/NMAVEN-119
             Project: NMaven
          Issue Type: New Feature
    Affects Versions: 0.14 (Unreleased)
            Reporter: jan ancajas


the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Commented: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137451#action_137451 ] 

Brett Porter commented on NMAVEN-119:
-------------------------------------

does this module work with trunk as well?

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>             Fix For: 0.14 (Unreleased), 0.16
>
>         Attachments: NMAVEN-assemblies-119-v2.patch, NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Updated: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated NMAVEN-119:
--------------------------------

    Fix Version/s: 0.14 (Unreleased)

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>             Fix For: 0.14 (Unreleased), 0.16
>
>         Attachments: NMAVEN-assemblies-119-v2.patch, NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Commented: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131013#action_131013 ] 

Shane Isbell commented on NMAVEN-119:
-------------------------------------

Just eyeballing this, it looks good. It needs the apache license headers attached to all the class files though.

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>         Attachments: NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Commented: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "jan ancajas (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137471#action_137471 ] 

jan ancajas commented on NMAVEN-119:
------------------------------------

yes. it should work

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>             Fix For: 0.14 (Unreleased), 0.16
>
>         Attachments: NMAVEN-assemblies-119-v2.patch, NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Updated: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "jan ancajas (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jan ancajas updated NMAVEN-119:
-------------------------------

    Attachment: NMAVEN-assemblies-119-v2.patch

attached: NMAVEN-assemblies-119-v2.patch

added some fixes since the initial patch:
1. ignore directory entries in .sln file with no csproj/vbproj associated w/ it 
2. normalize the reference name extracted from project file (e.g. "Castle.Windsor, Version=1.0.0.5, Culture=neutral, PublicKeyToken=407dd0808d44fbdc, processorArchitecture=MSIL" should only return "Castle.Windsor")
3. fix systemPath for dotnet-projects having their dependency included in the version control
4. add parent's relative path value so that NMaven can compile projects whose sub-module location is more than 1 directory level below from the parent pom 
5. improve project type support

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>         Attachments: NMAVEN-assemblies-119-v2.patch, NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Updated: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "jan ancajas (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jan ancajas updated NMAVEN-119:
-------------------------------

    Attachment: NMaven-assemblies-119.patch

attached initial draft:

for the design, i created  two modules 
i) console -  the CLI program 
ii.) engine - the pom generator

and then basically we can just create another module if we want a VS addin  and/or a maven plugin by importing the engine.

for the engine itself, the features are :
- generation for project dependencies/libraries
- use of nmaven-settings.xml`s  active compiler libraries  to  map the dependency libraries (using systemPath)
- the generated poms should compile. :)


to execute, append the parent solution file as program argument,  e.g.  :   NMaven.ProjectImporterEngine-0.2.exe  "C:\projects\a-multi-module-project\project1.sln"



> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>         Attachments: NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Commented: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "jan ancajas (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130720#action_130720 ] 

jan ancajas commented on NMAVEN-119:
------------------------------------

btw, this is dependent on NMAVEN-115  to resolve the compiler libraries being imported

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>         Attachments: NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Updated: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated NMAVEN-119:
--------------------------------

    Fix Version/s:     (was: 0.14 (Unreleased))
                   0.16

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>             Fix For: 0.14 (Unreleased), 0.16
>
>         Attachments: NMAVEN-assemblies-119-v2.patch, NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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

        

[jira] Updated: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated NMAVEN-119:
--------------------------------

    Fix Version/s: 0.14 (Unreleased)

> Ability to generate pom.xml file from an existing Visual Studio solution file
> -----------------------------------------------------------------------------
>
>                 Key: NMAVEN-119
>                 URL: http://jira.codehaus.org/browse/NMAVEN-119
>             Project: NMaven
>          Issue Type: New Feature
>    Affects Versions: 0.14 (Unreleased)
>            Reporter: jan ancajas
>             Fix For: 0.14 (Unreleased)
>
>         Attachments: NMAVEN-assemblies-119-v2.patch, NMaven-assemblies-119.patch
>
>
> the pom generator utility will accept the parent solution file, parses its corresponding csproj/vbproj files  then generate the pom for every module of the project

-- 
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