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

Posted to nmaven-dev@incubator.apache.org by Shane Isbell <sh...@gmail.com> on 2007/03/12 20:44:03 UTC

License implications of using integration package for VS

Has anyone on this list dealt with using the integration package for VS,
particularly for any open-source projects? The IDE integration features look
good, but I am uncertain as to all the license implications with the PLK and
thus reluctant to go this route without more info.

Shane

Re: License implications of using integration package for VS

Posted by Shane Isbell <sh...@gmail.com>.

Hi Brett,

I created this issue: http://jira.codehaus.org/browse/NMAVEN-13 and attached
a copy of the license.

Thanks,
Shane


On 3/12/07, Brett Porter <br...@apache.org> wrote:
>
> Can you point us at some license info?
>
> On 12/03/2007, at 1:44 PM, Shane Isbell wrote:
>
> > Has anyone on this list dealt with using the integration package
> > for VS,
> > particularly for any open-source projects? The IDE integration
> > features look
> > good, but I am uncertain as to all the license implications with
> > the PLK and
> > thus reluctant to go this route without more info.
> >
> > Shane
>

Re: License implications of using integration package for VS

Posted by Brett Porter <br...@apache.org>.

Can you point us at some license info?

On 12/03/2007, at 1:44 PM, Shane Isbell wrote:

> Has anyone on this list dealt with using the integration package  
> for VS,
> particularly for any open-source projects? The IDE integration  
> features look
> good, but I am uncertain as to all the license implications with  
> the PLK and
> thus reluctant to go this route without more info.
>
> Shane