The Maven team is pleased to announce the release of the Maven Plugin
Tools, including the maven-plugin-plugin, version 2.9
The Maven Plugin Plugin is used to create a Maven plugin descriptor
for any Mojo's found in the source tree, to include in the JAR.
http://maven.apache.org/plugins/maven-plu
This vote passes with binding +1 votes from Hervé, Olivier, and John
Casey. Sorry for the two misfires with the email.
On Mon, Sep 5, 2011 at 9:04 PM, Benson Margulies wrote:
> This vote passes with 3 +1 binding votes and no others.
>
>
> On Mon, Sep 5, 2011 at 8:59 PM, Benson Margulies
> wrote
This vote passes with 3 +1 binding votes and no others.
On Mon, Sep 5, 2011 at 8:59 PM, Benson Margulies wrote:
> By a strange coincidence, exactly three PMC members voted +1 and
> everyone else continued to estivate. So this vote passes, and I'll
> proceed.
>
> On Sat, Sep 3, 2011 at 8:46 AM, O
By a strange coincidence, exactly three PMC members voted +1 and
everyone else continued to estivate. So this vote passes, and I'll
proceed.
On Sat, Sep 3, 2011 at 8:46 AM, Olivier Lamy wrote:
> +1
>
> --
> Olivier
> Le 2 sept. 2011 18:44, "Benson Margulies" a écrit :
>> Hi,
>>
>> We solved 5 is
On Mon, Sep 5, 2011 at 2:32 PM, Igor Fedorenko wrote:
> Introducing tycho-specific lifecycles is not practically feasible.
That's not what I was suggesting. I was suggesting the use of a
convention on execution id's as a way of allowing order control.
I also was musing about signed-eclipse-plugi
Introducing tycho-specific lifecycles is not practically feasible. All
lifecycle phase names must be globally unit across all lifecycles, which
means we'd have to invent "tycho-compile", "tycho-validate" and so on.
This means we'd have to explain these new names to Tycho users. Many
standard maven
On Sun, Sep 4, 2011 at 10:48 PM, Igor Fedorenko wrote:
> I agree that adding new phase (or phases) does not look like a scalable
> solution. For example, in addition to signing,
Tycho could add more lifecycles. Since those are selected by
'packaging', however, and not variable by profile, it woul
Excerpts from Stanislav Ochotnicky's message of Mon Sep 05 10:35:17 +0200 2011:
> Hi everyone,
>
> Currently Maven includes test dependencies in resolving graph even when
> -Dmaven.test.skip is used. It's unnecessary and sub-optimal when big
> test dependencies have to be downloaded to local cache
Hi everyone,
Currently Maven includes test dependencies in resolving graph even when
-Dmaven.test.skip is used. It's unnecessary and sub-optimal when big
test dependencies have to be downloaded to local cache. As far as I know
Maven 2.X didn't have this problem, so I'd guess this is a sort of
regr
