Re: Deploying Microsoft framework dlls to an internal remote repo

[caulene]

On Wed, 28 May at 8:39 PM, Wendy Smoak wsmoak@... wrote:

>So... that sounds like it would be appropriate to add a reference in
>Visual Studio that does *not* need to be in the pom, because the
>command-line csc compiler would already know about it.? Correct?

If the framework dlls are not specified in the pom, how would a project team specify the version of the .NET framework to be used??

One of the big selling points of Maven (and NMaven) is dependency management and reproduceability ... if the compiler just uses the default path to pick up the framework, it would negate the value.? Any thoughts?

-- Caulene

[Shane Isbell]

On Tue, Jun 17, 2008 at 10:06 AM, <caulene@...> wrote:

> On Wed, 28 May at 8:39 PM, Wendy Smoak wsmoak@... wrote:
>
> >So... that sounds like it would be appropriate to add a reference in
> >Visual Studio that does *not* need to be in the pom, because the
> >command-line csc compiler would already know about it.? Correct?
>
> If the framework dlls are not specified in the pom, how would a project
> team specify the version of the .NET framework to be used??

Check the information here on specifying the framework version in 0.14.
http://incubator.apache.org/nmaven/0.14/environment-configuration.html#Sample%20Configuration%20Files

Also through the compiler-plugins.xml you can create a profile that uses a
different assembly root (this is how the compact profile is supported).

In 0.16 we will be using Maven toolchains to support different .NET
versions.

Shane

One of the big selling points of Maven (and NMaven) is dependency management
and reproduceability ... if the compiler just uses the default path to pick
up the framework, it would negate the value.? Any thoughts?

-- Caulene