Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: error (nike.apache.org: local policy)
MIME-Version: 1.0
Sender: kristian.rosenvold@zenior.no
In-Reply-To: <54F56258.70106@gmx.de>
References: <4738607.51Ps7n7Nog@herve-desktop>
	<CAJZRQKxQ1-a8AG=mOBRKtn_aRpRVUHD4jYaPbNuCYGMq87A=EQ@mail.gmail.com>
	<54F56258.70106@gmx.de>
Date: Tue, 3 Mar 2015 08:30:32 +0100
Message-ID: 
 <CAJZRQKwb8vw1YJ947DwceZ5Wgg9WnPuhmJ8mGObJHpTRogHJbw@mail.gmail.com>
Subject: Re: status of last plugins release with Maven 2.2.1 and Java 5
 requirements
From: Kristian Rosenvold <kristian.rosenvold@gmail.com>
To: Maven Developers List <dev@maven.apache.org>, info@soebes.de
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'm really good with =C3=BCmlauts and pi=C3=B1atas, I'll fix it :)

Kristian


2015-03-03 8:27 GMT+01:00 Karl Heinz Marbaise <khmarbaise@gmx.de>:
> Hi Kristian,
>
> jar-plugin is only one issue left....where i would like to get help......
>
>
>
> On 3/3/15 8:15 AM, Kristian Rosenvold wrote:
>>
>> I can do jar-plugin and verifier-plugin, will do that together with
>> assembly 2.6.4 later this week/this weekend.
>>
>> Kristian
>>
>> 2015-03-03 5:45 GMT+01:00 Herv=C3=A9 BOUTEMY <herve.boutemy@free.fr>:
>>>
>>> Hi Maven devs,
>>>
>>> We're now near the objective [1]
>>>
>>> On 49 plugins, 37 reached the target (with m-pmd-p requiring Java 6
>>> instead of
>>> 5) and 2 already jumped to Maven 3.0 requirement
>>> And maven-stage-plugin is on vote
>>>
>>> =3D 40 from 49: more than 80% of the job is done, great!
>>>
>>> Thank you to those who worked on this, particularly Karl Heinz who did =
a
>>> great
>>> part of it.
>>>
>>> This lets 9 plugins to release:
>>> - maven-scm-plugin
>>> - maven-docck-plugin
>>> - maven-jar-plugin
>>> - maven-patch-plugin
>>> - maven-verifier-plugin
>>> - maven-archetype-plugin
>>> - maven-eclipse-plugin
>>> - maven-compiler-plugin
>>> - maven-doap-plugin
>>>
>>> Are there volunteers on each one, please?
>>>
>>> IMHO, we should write down the list of plugins and versions to the Mave=
n
>>> 2 EOL
>>> page [2], to clearly store this info while it is available (copy/pastin=
g
>>> the
>>> report) and link to versioned documentation of every plugin: if no
>>> objection,
>>> I'll do it in a few days.
>>>
>>> I think that we should also have a convention on each plugin (and perha=
ps
>>> each
>>> component) to document requirements history: I have no precise idea on
>>> the way
>>> to do that. Addition to plugin-info.html (with parameters in pom.xml)?
>>> Add a
>>> standard paragraph in index.html (and update maven-docck-plugin to chec=
k
>>> for
>>> it)? Any idea?
>>>
>>> Then we'll be able to upgrade to Maven 3.0 and Java 6 requirements in
>>> parent
>>> pom.
>>> And of course announce to users the plan towards plugins 3.x for Maven
>>> 3.0 and
>>> JDK 6 requirement (and remember full Maven 2.x EOL, that is not only
>>> Maven,
>>> but also plugins).
>>>
>>> Really good job: this gives a great consistency step that was lacking
>>> before.
>>>
>>> Regards,
>>>
>>> Herv=C3=A9
>>>
>>> [1]
>>> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site=
/dist-tool-prerequisites.html
>>>
>>> [2] http://maven.apache.org/maven-2.x-eol.html
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org