Hi Chris,

The http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/resources/META-INF/plexus/components.xml refers to MNG-4384[1] by its role-hints.
That's the only option you have to decrypt passwords with Maven 2.2.0+.
This can be removed once the maven-release-plugin requires at least Maven3

Robert

[1] http://jira.codehaus.org/browse/MNG-4384

Op Wed, 10 Jul 2013 02:48:20 +0200 schreef Chris Graham <[email protected]>:

Thanks for the explanation!

Ah, annotations, that also threw me.

But what really threw me, was that there is already a components.xml where
it should be, META-INF/plexus/components.xml

ie:

http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/resources/META-INF/plexus/components.xml

So why would we not merge them manually, and still keep the existing build
process?

-Chris



On Wed, Jul 10, 2013 at 3:18 AM, Robert Scholte <[email protected]>wrote:

Hi Chris,

Although I haven't introduced this file, I can think of the reasons of the
filename and its location.

The components-fragment is only a small part of the plexus configuration. It defines all release phases per goal and also configures all these phases (some of them have the same implementation, just different configuration).
This can't be extracted from Java code, and you probably don't want too.
But this module has a lot more Plexus components, which are easier to
maintain with annotations.
In the end these configurations need to be merged. So the
components-fragment.xml is indeed a fragment of all plexus component.

The components-fragment.xml is actually a resource, but as said: it should
be merged before being added to the archive. So src/main/resource is not
the right spot, although it is part of the main (re)sources.

Maybe a subfolder of src/main would have been a better location, but which
one?

Robert


Op Tue, 09 Jul 2013 12:00:27 +0200 schreef Chris Graham <
[email protected]>:


 :-)

I totally missed that. Thanks now it makes perfect sense.

I'll have a closer look tomorrow.

-Chris

Sent from my iPhone

On 09/07/2013, at 4:19 PM, Olivier Lamy <[email protected]> wrote:

 see the pom: http://svn.apache.org/repos/**
asf/maven/release/trunk/maven-**release-manager/pom.xml<http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/pom.xml>

plexus-maven-plugin merge the content
I agree that's not the usual place :-)

2013/7/9 Chris Graham <[email protected]>:

Hi All.

The full path is:
http://svn.apache.org/repos/**asf/maven/release/trunk/maven-**
release-manager/src/main/**components-fragment.xml<http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/components-fragment.xml>

Can someone please explain to me how this file is used (and why it's not
under the META-INF/plexus dir [at the very least]) ?

I'm struggling to see how it is incorporated into the build.

Also why -fragments? it's a complete XML file...

-Chris




--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

------------------------------**------------------------------**
---------
To unsubscribe, e-mail: [email protected].**org<[email protected]>
For additional commands, e-mail: [email protected]


------------------------------**------------------------------**---------
To unsubscribe, e-mail: [email protected].**org<[email protected]>
For additional commands, e-mail: [email protected]


------------------------------**------------------------------**---------
To unsubscribe, e-mail: [email protected].**org<[email protected]>
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to