You are viewing a plain text version of this content. The canonical link for it is here.

Posted to nmaven-issues@incubator.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/09/14 22:00:49 UTC

[jira] Updated: (NMAVEN-104) Support .NET Assembly Manifest

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

Brett Porter updated NMAVEN-104:
--------------------------------

    Component/s: Core components

> Support .NET Assembly Manifest
> ------------------------------
>
>                 Key: NMAVEN-104
>                 URL: http://jira.codehaus.org/browse/NMAVEN-104
>             Project: NMaven
>          Issue Type: New Feature
>          Components: Core components
>            Reporter: Pavel Znamenacek
>            Assignee: Shane Isbell
>             Fix For: Future
>
>
> Add support for .NET Assembly Manifest in all of its forms, single file assembly (usually linked into assembly .dll) and multi-file assembly (more important part of this improvement). See more at http://msdn2.microsoft.com/en-us/library/1w45z383(VS.80).aspx.
> I find that all process of manifest generation could be automatic and also argument from life-cycles of a project via the developer inputs aka command line, POM, sources, profiles, etc.
> This should enable NMaven to build up such assembly which has custom files beside such as xmls or picture files or others.
> The large scaled project uses multi-file assembly often.

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