Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v746.2)
In-Reply-To: <c278ac970603201301q6baf3494ke894f2816b82e657@mail.gmail.com>
References: <c278ac970603201301q6baf3494ke894f2816b82e657@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C4985F58-1E6F-45A8-89E0-BDDB57FB0ED7@iq80.com>
Content-Transfer-Encoding: 7bit
From: Dain Sundstrom <dain@iq80.com>
Subject: Re: Migrating geronimo-plugins to M2
Date: Mon, 20 Mar 2006 14:52:33 -0800
To: dev@geronimo.apache.org

I think we will need to support our user oriented m1 plugins for a  
long time as not everyone is going to switch to m2 quickly.  Also we  
need ant versions of these plugins for those that use Ant.

-dain

On Mar 20, 2006, at 1:01 PM, Prasad Kashyap wrote:

> We have now reached the stage where we have to migrate the plugins. In
> the modules, the same code was used to build both m1 and m2 artifacts.
> Unlike the modules, the code in the plugins would have to change as we
> create mojos out of them. But the existing code has to be supported
> until we have completely 'm2-ized'  our build.
>
> The BIG question :
> As we start migrating the plugins, where do we drop them ?
>
> [ ] Option 1: create a new directory for m2 plugins. (eg.
> geronimo/m2-plugins). Drop m2 plugins here. In the future, delete
> existing geronimo/plugins and rename the m2-plugins to plugins.
>
> [ ] Option 2: drop m2 plugins in the same directories as their m1
> counterparts. The m2 code will be in a different package structure.
> The m2 artifact will have a different groupid. Ensure different  jars
> get built. Live with the harmless possibility of the m1 jar carrying
> m2 classes and vice-versa.
>
> [ ] Option 3: ??
>
>
> Cheers
> Prasad