incubator-nmaven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shane Isbell" <shane.isb...@gmail.com>
Subject Re: Merging New Work into Trunk
Date Wed, 12 Dec 2007 04:14:16 GMT
On Dec 11, 2007 7:58 PM, Brett Porter <brett@apache.org> wrote:

> Is this a merge, or a replacement?


This would be a merge operation but most of the modules currently in the
trunk would be going away.


>
>
> I think this is generally the right idea - I was going to suggest it
> myself after some consideration earlier today. However I'd like 72
> hours to review the new code as I'm still catching up.
>
> Is the branch POM-compatible with the current trunk? IMO, the upgrade
> path for any current users should be no more than deleting their local
> repository and updating any versions they may have hardcoded.


No, the branch pom is not compatible. As part of this I would copy the
branch sandbox contents into the root of the branch, delete unneeded
directories and then merge to trunk.

Shane


>
>
> - Brett
>
> On 12/12/2007, at 2:44 PM, Shane Isbell wrote:
>
> > We finally have working code for that will integrate nicely with
> > Maven. It's
> > fairly limited at the moment and only supports compiling and
> > installing of
> > C#. I would like to see what people thought about merging it over
> > into the
> > trunk, with the idea of getting an initial release out, being that
> > we've
> > been in the incubator for a year. This would involve tagging the
> > current
> > trunk so that people can still build off of it, as it offers a great
> > deal of
> > functionality, including Visual Studio addin support.
> >
> > Shane
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message