[
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
