directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot" ...@marcelot.net>
Subject Re: [studio-plugin] new location
Date Fri, 19 Sep 2008 14:48:23 GMT
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-----
>

Mime
View raw message