You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Lars Corneliussen (Commented) (JIRA)" <ji...@apache.org> on 2011/11/23 11:27:40 UTC
[jira] [Commented] (NPANDAY-405) Allow to build multiple
configurations in one build (Multi-targeting)
[ https://issues.apache.org/jira/browse/NPANDAY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155812#comment-13155812 ]
Lars Corneliussen commented on NPANDAY-405:
-------------------------------------------
We should consider using the same abbreviations as NuGet: http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package#Grouping_Assemblies_by_Framework_Version
> Allow to build multiple configurations in one build (Multi-targeting)
> ---------------------------------------------------------------------
>
> Key: NPANDAY-405
> URL: https://issues.apache.org/jira/browse/NPANDAY-405
> Project: NPanday
> Issue Type: New Feature
> Components: Maven Plugins
> Reporter: Lars Corneliussen
> Fix For: Backlog
>
>
> It would be great, if 'mvn compile' just compiled different configuration combinations in one build.
> Just as an example, look at the log4net-distribution. How would we produce that using NPanday today?
> {code}
> log4net-1.2.10/bin
> log4net-1.2.10/bin/cli
> log4net-1.2.10/bin/cli/1.0
> log4net-1.2.10/bin/cli/1.0/release
> log4net-1.2.10/bin/cli/1.0/release/log4net.dll
> log4net-1.2.10/bin/cli/1.0/release/log4net.xml
> log4net-1.2.10/bin/mono
> log4net-1.2.10/bin/mono/1.0
> log4net-1.2.10/bin/mono/1.0/debug
> log4net-1.2.10/bin/mono/1.0/debug/log4net.dll
> log4net-1.2.10/bin/mono/1.0/debug/log4net.dll.mdb
> log4net-1.2.10/bin/mono/1.0/debug/log4net.xml
> log4net-1.2.10/bin/mono/1.0/release
> log4net-1.2.10/bin/mono/1.0/release/log4net.dll
> log4net-1.2.10/bin/mono/1.0/release/log4net.xml
> log4net-1.2.10/bin/mono/2.0
> log4net-1.2.10/bin/mono/2.0/debug
> log4net-1.2.10/bin/mono/2.0/debug/log4net.dll
> log4net-1.2.10/bin/mono/2.0/debug/log4net.dll.mdb
> log4net-1.2.10/bin/mono/2.0/debug/log4net.xml
> log4net-1.2.10/bin/mono/2.0/release
> log4net-1.2.10/bin/mono/2.0/release/log4net.dll
> log4net-1.2.10/bin/mono/2.0/release/log4net.xml
> log4net-1.2.10/bin/net
> log4net-1.2.10/bin/net/1.0
> log4net-1.2.10/bin/net/1.0/debug
> log4net-1.2.10/bin/net/1.0/debug/log4net.dll
> log4net-1.2.10/bin/net/1.0/debug/log4net.pdb
> log4net-1.2.10/bin/net/1.0/debug/log4net.xml
> log4net-1.2.10/bin/net/1.0/release
> log4net-1.2.10/bin/net/1.0/release/log4net.dll
> log4net-1.2.10/bin/net/1.0/release/log4net.xml
> log4net-1.2.10/bin/net/1.1
> log4net-1.2.10/bin/net/1.1/debug
> log4net-1.2.10/bin/net/1.1/debug/log4net.dll
> log4net-1.2.10/bin/net/1.1/debug/log4net.pdb
> log4net-1.2.10/bin/net/1.1/debug/log4net.xml
> log4net-1.2.10/bin/net/1.1/release
> log4net-1.2.10/bin/net/1.1/release/log4net.dll
> log4net-1.2.10/bin/net/1.1/release/log4net.xml
> log4net-1.2.10/bin/net/2.0
> log4net-1.2.10/bin/net/2.0/debug
> log4net-1.2.10/bin/net/2.0/debug/log4net.dll
> log4net-1.2.10/bin/net/2.0/debug/log4net.pdb
> log4net-1.2.10/bin/net/2.0/debug/log4net.xml
> log4net-1.2.10/bin/net/2.0/release
> log4net-1.2.10/bin/net/2.0/release/log4net.dll
> log4net-1.2.10/bin/net/2.0/release/log4net.xml
> log4net-1.2.10/bin/netcf
> log4net-1.2.10/bin/netcf/1.0
> log4net-1.2.10/bin/netcf/1.0/debug
> log4net-1.2.10/bin/netcf/1.0/debug/log4net.dll
> log4net-1.2.10/bin/netcf/1.0/debug/log4net.pdb
> log4net-1.2.10/bin/netcf/1.0/debug/log4net.xml
> log4net-1.2.10/bin/netcf/1.0/release
> log4net-1.2.10/bin/netcf/1.0/release/log4net.dll
> log4net-1.2.10/bin/netcf/1.0/release/log4net.xml
> log4net-1.2.10/bin/sscli
> log4net-1.2.10/bin/sscli/1.0
> log4net-1.2.10/bin/sscli/1.0/debug
> log4net-1.2.10/bin/sscli/1.0/debug/log4net.dll
> log4net-1.2.10/bin/sscli/1.0/debug/log4net.ildb
> log4net-1.2.10/bin/sscli/1.0/release
> log4net-1.2.10/bin/sscli/1.0/release/log4net.dll
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira