Hi, Brian.
It's so nice of you to remind us. IIRC, the original problem was due to the
newer versions of the maven-dependency-plugin as we referenced the SNAPSHOT
version of the plugin in M2 driver. I think we have fixed the wrong
configuration in the latest code but I'll double-check.
BTW, do you know if there is a way in the pom.xml to use LATEST RELEASED
plugin? Maven takes the latest SNAPSHOTs if the version is not explicitly
specified. As we know, it's very risky for a release to depend on SNAPSHOTs.
Thanks,
Raymond
----- Original Message -----
From: "Brian Fox" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, March 29, 2007 4:31 PM
Subject: Tuscany Unpack issues
Hi,
I'm one of the Maven developers next-door at apache and the main
developer for the maven-dependency-plugin. We've had a few requests
recently from Tuscany users who have problems with the instructions or
with the pom. (I haven't found the instructions yet so I can't be
positive) You can see this thread for more info:
http://www.nabble.com/mvn-dependency%3Aunpack-tf3436260s177.html#a9580702
It seems that the instructions indicate to run "mvn
dependency:unpack", however the POM isn't setup correctly to do this.
I recently added a FAQ to the site as well as more examples for this
use case here:
http://maven.apache.org/plugins/maven-dependency-plugin/faq.html#question
I figured I'd pop in to see if we can try to get this fixed up so the
users don't have a bad experience both with Tuscany and Maven. Let me
know if there's anything I can do to help.
-Brian
---------------------------------------------------------------------
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]
