Re: Unpack issues with Tuscany
On 3/30/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: Simon, The dependency:unpack and copy goals are intended to be used by binding to a phase in the pom. They use custom objects (ArtifactItems) that can't be defined on the CLI. If you want to run it from the CLI, you have to first add the configuration to the pom as described on the link I sent below. Another alternative that doesn't require pom config would be unpack-dependencies but that will grab all dependencies...there are some flags that could be used to filter them that are doc'd on the plugin page. Based on what it looks like you're doing, you want unpack but just need to put the config in the pom. Alternatively, you could add it to the build and make it happen for the user automatically. -Original Message- From: Simon Laws [mailto:[EMAIL PROTECTED] Sent: Friday, March 30, 2007 12:03 PM To: tuscany-dev@ws.apache.org Subject: Re: Unpack issues with Tuscany On 3/29/07, Brian Fox <[EMAIL PROTECTED]> wrote: > > 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#a9580 > 702 > > 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#quest > ion > > 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] > > Hi Brian, Thanks for dropping by. I worked with Muhwas to get him a > work around so he could get our M2 tests running. I couldn't get the Tuscany M2 samples to work either following the instructions as documented in the readme. It specifically says to do "mvn dependecy:unpack" but I can't find anywhere that the maven-dependency-plugin is configured in the pom hierarchy for our M2 release. What is the intended behaviour if you do "mvn dependecy:unpack" against a pom with no maven-dependency-plugin configuration? Should it do anything sensible. I wasn't very close to the M2 release but I know people tried the samples before cutting the tag so something strange is going on. Anyhow I suspect that it's a Tuscany problem and not a Maven problem but it needs more investigation. If nothing else we need to fix our documentation! Thanks again for posting this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Great, thanks for that info Brian. Will take a look at it and see if we can come up with a suitable fix. Regards Simon
RE: Unpack issues with Tuscany
Simon, The dependency:unpack and copy goals are intended to be used by binding to a phase in the pom. They use custom objects (ArtifactItems) that can't be defined on the CLI. If you want to run it from the CLI, you have to first add the configuration to the pom as described on the link I sent below. Another alternative that doesn't require pom config would be unpack-dependencies but that will grab all dependencies...there are some flags that could be used to filter them that are doc'd on the plugin page. Based on what it looks like you're doing, you want unpack but just need to put the config in the pom. Alternatively, you could add it to the build and make it happen for the user automatically. -Original Message- From: Simon Laws [mailto:[EMAIL PROTECTED] Sent: Friday, March 30, 2007 12:03 PM To: tuscany-dev@ws.apache.org Subject: Re: Unpack issues with Tuscany On 3/29/07, Brian Fox <[EMAIL PROTECTED]> wrote: > > 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#a9580 > 702 > > 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#quest > ion > > 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] > > Hi Brian, Thanks for dropping by. I worked with Muhwas to get him a > work around so he could get our M2 tests running. I couldn't get the Tuscany M2 samples to work either following the instructions as documented in the readme. It specifically says to do "mvn dependecy:unpack" but I can't find anywhere that the maven-dependency-plugin is configured in the pom hierarchy for our M2 release. What is the intended behaviour if you do "mvn dependecy:unpack" against a pom with no maven-dependency-plugin configuration? Should it do anything sensible. I wasn't very close to the M2 release but I know people tried the samples before cutting the tag so something strange is going on. Anyhow I suspect that it's a Tuscany problem and not a Maven problem but it needs more investigation. If nothing else we need to fix our documentation! Thanks again for posting this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unpack issues with Tuscany
On 3/29/07, Brian Fox <[EMAIL PROTECTED]> wrote: 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] Hi Brian, Thanks for dropping by. I worked with Muhwas to get him a work around so he could get our M2 tests running. I couldn't get the Tuscany M2 samples to work either following the instructions as documented in the readme. It specifically says to do "mvn dependecy:unpack" but I can't find anywhere that the maven-dependency-plugin is configured in the pom hierarchy for our M2 release. What is the intended behaviour if you do "mvn dependecy:unpack" against a pom with no maven-dependency-plugin configuration? Should it do anything sensible. I wasn't very close to the M2 release but I know people tried the samples before cutting the tag so something strange is going on. Anyhow I suspect that it's a Tuscany problem and not a Maven problem but it needs more investigation. If nothing else we need to fix our documentation! Thanks again for posting this. Simon
Unpack issues with Tuscany
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]
