let's do that. I'll test it on archetype level and then we'll see to move
it later on plugins or maven levels
On Mon, Jul 8, 2013 at 11:02 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I think ultimately at maven parent, but if you want to play at a less wide
> level first I t
I think ultimately at maven parent, but if you want to play at a less wide
level first I think that could be a good plan too
On 8 July 2013 09:59, Arnaud Héritier wrote:
> yes, far from me the idea to have such controls for every builds :-)
> either in a dedicated profile launched manually by c
yes, far from me the idea to have such controls for every builds :-)
either in a dedicated profile launched manually by committers (and CI?) or
in the release profile
Something to add at which level ? plugins parent ? maven parent ?
On Mon, Jul 8, 2013 at 10:52 AM, Stephen Connolly <
stephen.alan
On 8 July 2013 09:23, Arnaud Héritier wrote:
> Hi,
>
> Last night I introduced by error a dependency requiring Java 6 in the
> archetype plugin whereas we are always supposed to support Java 5 (Yes we
> can :-) )
> Myself I don't have anymore a Java 5 on my computer and I'm often using
> Java
Hi,
Last night I introduced by error a dependency requiring Java 6 in the
archetype plugin whereas we are always supposed to support Java 5 (Yes we
can :-) )
Myself I don't have anymore a Java 5 on my computer and I'm often using
Java 7 by default and I'm probably not the only one. Even if we
