Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates
 209.85.217.19 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=Grjpke0uybn3i3b9o22CMaSUYJeMl8bTslONGFUNDzNKsK3KOy7NEe5mJd3axj4V1c
         Ke0RoO6fHpcIDNLIvE3P24Rp4WtP7byUniX9paTnNhPKDBejFeVad+8b7vdgBZO8pPZd
         WL3KnCzH4nbIGk++c0IhiQ7GUdWyzEa7oCUKA=
Message-ID: <98d8c0860809190748m50fc6ec0k8a0875e2edc3ce87@mail.gmail.com>
Date: Fri, 19 Sep 2008 16:48:23 +0200
From: "Pierre-Arnaud Marcelot" <pa@marcelot.net>
Sender: pajbam@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [studio-plugin] new location
In-Reply-To: <48D3B791.90605@otego.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_58063_3663827.1221835703130"
References: <48D3B791.90605@otego.com>

------=_Part_58063_3663827.1221835703130
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I think I'd vote for solution b.
It keeps each Maven plugin independant and easy to release.

Thanks,
Pierre-Arnaud

On Fri, Sep 19, 2008 at 4:30 PM, Felix Knecht <felix@otego.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> We still do have the problem when releasing/tagging the studio-plugin
> interfere with the studio releasing/tagging.
> - From my POV there are to options
>
> a) Move it as single project to the same level like
> apachds/studio/shared/...
>  studio
>  \ branches
>  \ tags
>  \ trunk
>
>
> b) Create a general plugin project and move it into this
>  plugin
>  \ studio
>    \ branches
>    \ tags
>    \ trunk
>  \ foo
>    \ branches
>    \ tags
>    \ trunk
>
> WDOT?
>
> Felix
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkjTt5EACgkQ2lZVCB08qHE5kgCfW+WVgHpKoQnDAIhyzR0QvqZA
> aKUAn32UsdnrWkJZRENtzekUru77PzDN
> =vhgO
> -----END PGP SIGNATURE-----
>

------=_Part_58063_3663827.1221835703130
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi,<br><br>I think I&#39;d vote for solution b.<br>It keeps each Maven plugin independant and easy to release.<br><br>Thanks,<br>Pierre-Arnaud<br><br><div class="gmail_quote">On Fri, Sep 19, 2008 at 4:30 PM, Felix Knecht <span dir="ltr">&lt;<a href="mailto:felix@otego.com">felix@otego.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
We still do have the problem when releasing/tagging the studio-plugin interfere with the studio releasing/tagging.<br>
- From my POV there are to options<br>
<br>
a) Move it as single project to the same level like apachds/studio/shared/...<br>
 &nbsp;studio<br>
 &nbsp;\ branches<br>
 &nbsp;\ tags<br>
 &nbsp;\ trunk<br>
<br>
<br>
b) Create a general plugin project and move it into this<br>
 &nbsp;plugin<br>
 &nbsp;\ studio<br>
 &nbsp; &nbsp;\ branches<br>
 &nbsp; &nbsp;\ tags<br>
 &nbsp; &nbsp;\ trunk<br>
 &nbsp;\ foo<br>
 &nbsp; &nbsp;\ branches<br>
 &nbsp; &nbsp;\ tags<br>
 &nbsp; &nbsp;\ trunk<br>
<br>
WDOT?<br>
<br>
Felix<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.9 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br>
iEYEARECAAYFAkjTt5EACgkQ2lZVCB08qHE5kgCfW+WVgHpKoQnDAIhyzR0QvqZA<br>
aKUAn32UsdnrWkJZRENtzekUru77PzDN<br>
=vhgO<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div>

------=_Part_58063_3663827.1221835703130--