Hi there,

just for the record to this thread:
I wrote consumer-maven-plugin and added it to MOJOs sandbox.
The plugin allows to generate a consumer POM and apply it to the current MavenProject (via setFile). So we can already test various impacts of what can, will and should happen when a "consumer POM" is installed, signed, deployed instead of the original pom.xml file that can later on be in future model formats.

See thread on dev mojo with subject "consumer-maven-plugin added to sandbox".
Hope to hear from you.

Kind regards
  Jörg

Am 24.11.2013 23:04, schrieb Barrie Treloar:
On 25 November 2013 03:28, Stephen Connolly
<[email protected]> wrote:
[del]
Given that we have decided that the reporting stuff possibly was a
mistake... Well let's drop that

Given that profiles do not make sense in deployed poms... Drop them too

We think <repositories> is evil... Let's drop that... We've dropped build
and reporting=> no need for pluginRepositories at all so.
I'm in favour of cleaning out elements that cause problems when they
are tweaked in a the non-Maven Way.
The emails to the users list would be reduce and there is less chance
of causing confusion.

Applying the "current" best practises and baking them into the poms is
a good thing.



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to