I've linked the two issues related to this that I know about in JIRA
(MDEPLOY-94, MNG-3057), but I basically agree that the patch would look
like what Brett has shown in terms of how to implement it. I'm not as
familiar with the ArtifactTransformation system any more,
unfortunately...too many things to keep in my head at once, I guess.
I'll look at it, but I'm not sure whether there is an associated
ArtifactMetadataTransformation we can take advantage of. Since POMs are
actually considered metadata, we'd have to use a metadata transformation
and not an artifact transformation.
It's starting to look like we should move forward on this for 2.1.0 and
take our best shot...if we're missing critical use cases, we can account
for them and fix things in 2.1.1 or whatever...a new release with a
super-small objective.
...It would be really nice to have a fine-grained settings section
somewhere (*cough* settings.xml?) that we could use to opt-out of this
and the parallel resolution stuff, just in case. Something like an
enable-experimental-features flag might even do the trick.
I can take another look at these issues once I'm finished testing
MNG-3971. If you have some progress you can post as a partial patch,
that might speed things up.
-john
jaxzin wrote:
Brett, thanks so much for pointing me a this revision. I'll take a look and
hopefully come up with a solution from it!
Thanks,
Brian
brettporter wrote:
You'll probably find it easier to simply rebuild Maven :)
In some ways, the patch should look similar to this:
http://svn.apache.org/viewvc?view=rev&revision=682589
Cheers,
Brett
On 09/02/2009, at 11:00 AM, jaxzin wrote:
Thanks Brian! I was just stumbling into that so I appreciate you
clarifying
it.
Regards,
Brian
Brian E Fox wrote:
The easiest way is to put it in your maven install in /lib and then
edit
the m2.conf file to put your jar in the list before uberjar.
-----Original Message-----
From: jaxzin [mailto:[email protected]]
Sent: Sunday, February 08, 2009 9:13 PM
To: [email protected]
Subject: How do I test patches to maven-artifact-manager?
I'm trying to implement a fix for
http://jira.codehaus.org/browse/MDEPLOY-94
but I'm having trouble overriding
'org.apache.maven:maven-artifact-manager'
because it's packaged inside the maven-2.0.x-uber.jar. Am I missing
something simple for testing and deploying changes to
maven-artifact-manager
or other artifacts that are bundled in the bootstrap uber jar that is
part
of the Maven install?
Thanks,
Brian
--
View this message in context:
http://www.nabble.com/How-do-I-test-patches-to-maven-artifact-manager--t
p21906071p21906071.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
View this message in context:
http://www.nabble.com/How-do-I-test-patches-to-maven-artifact-manager--tp21906071p21906398.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
