[
https://issues.apache.org/jira/browse/NPANDAY-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095896#comment-13095896
]
Brett Porter commented on NPANDAY-468:
--------------------------------------
the build tasks issue has already been fixed in trunk
> npanday does not respect scope
> ------------------------------
>
> Key: NPANDAY-468
> URL: https://issues.apache.org/jira/browse/NPANDAY-468
> Project: NPanday
> Issue Type: Question
> Components: Maven Plugins
> Affects Versions: 1.4-incubating
> Environment: windows 7, maven 2.2.1
> Reporter: sergio rupena
>
> When you add a dependency with scope 'runtime', npanday will pass that
> dependency to the compiler.
> Example:
> <dependency>
> <groupId>Foo</groupId>
> <artifactId>MyAssembly.dll</artifactId>
> <version>1.0-SNAPSHOT</version>
> <type>dotnet-library</type>
> <scope>runtime</scope>
> </dependency>
> This will trigger the following command option for the compiler:
> /reference:D:\Temp\project\target\MyAssembly.dll
> The scope "runtime" means that this assembly is not needed at compile time so
> I would not expect npanday to add a reference to it.
> Also I wonder why npanday uses by default references like
> Microsoft.Build.Tasks.v3.5.dll to compile my assemblies.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
