Re: separate releases for Maven plugins & VS integration (was: [NPanday] NPanday 2.0 Road Map)

[Brett Porter <br...@apache.org>]

On 12/10/2010, at 11:50 AM, Josimpson Ocaba wrote:

>> 
>> How about splitting the VS integration and the Maven plugins into two
>> separate releases / trunks? Can't remember if I brought that up
>> before, or if it were already ruled out - if so, just point me to the
>> thread :)
> 
> I don't recall this being brought up before. I'm not really sure if this would be a good idea since there are certain functionalities that would cross over from plugins to VS integration. 
> 

Which functionality is that? I'm not hugely familiar with developing on the VS addin, but it seemed that many fixes for it are isolated to it's codebase (and the project importer assemblies), and not the maven plugins, core libraries, and .net-authored maven plugins and their assemblies.

Part of the reason I was thinking this is that in some situations the addin operates separately, by working with Maven projects that have POMs referencing earlier NPanday plugin versions.

- Brett

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/