On Wed, May 28, 2008 at 8:43 AM, Shane Isbell <[EMAIL PROTECTED]> wrote:

>> Should it be necessary to put the Microsoft framework dlls in a remote
>> repository, or is NMaven supposed to find them in (for example)
>> C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 ?
>>
> To the best of my knowledge, the .NET framework license prohibits
> redistribution of the framework libraries.

Apparently the licensing thing has been worked out by the relevant
parties-- so assume it's not an issue for the sake of discussion.
(And it's a private internal repository in any case.)

Even so, now is the time to set the convention for the groupId and
artifactIds by putting poms into the repository without the dlls--
like we did with the Sun jars for Java builds even though the license
prohibited putting the jars in the central repo.

So... does Microsoft.NET.Framework sound okay for a groupId?

-- 
Wendy




-- 
Wendy

Reply via email to