[
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
