Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of
 stephen.alan.connolly@gmail.com designates 209.85.218.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <trinity-530ce2e4-cf74-4a60-9c18-e3d8ef4ceb5f-1412939328474@3capp-gmx-bs29>
References: 
 <trinity-530ce2e4-cf74-4a60-9c18-e3d8ef4ceb5f-1412939328474@3capp-gmx-bs29>
Date: Fri, 10 Oct 2014 12:15:07 +0100
Message-ID: 
 <CA+nPnMyj5rhRwvBPeUi27LZxUwOwFyuwu-pmrE0S0MXwHb4zdg@mail.gmail.com>
Subject: Re: Maven plugin naming pattern
From: Stephen Connolly <stephen.alan.connolly@gmail.com>
To: Maven Developers List <dev@maven.apache.org>
Content-Type: multipart/alternative; boundary=001a113d74ea5ae1a105050fa9dc

--001a113d74ea5ae1a105050fa9dc
Content-Type: text/plain; charset=UTF-8

They should rename going forward.

At some point (probably we could do so now) we will turn on enforcement in
the maven-plugin-plugin.

If they have not renamed then they will be stuck with the older tooling.

On 10 October 2014 12:08, Michael Osipov <1983-01-06@gmx.net> wrote:

> Hi folks,
>
> how do we actually proceed with third-party plugins which do not comply to
> our naming pattern [1]?
> Given that a plugin has been created before this document has beeen first
> published 2013-01-02.
>
> Should they simply add a disclaimer for legacy reasons? What about plugins
> on Central created after that date?
>
> Michael
>
> [1]
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

--001a113d74ea5ae1a105050fa9dc--