My experience has been that the first invocation of the antrun plugin sets the plugins dependencies. Because of this, all of the poms that use the antrun plugin have the same list of dependencies specified for it.
Mildly annoying, but it gets us around the problem for now. I'm pretty sure there is an existing JIRA for the problem, but I don't have the number off the top of my head. Hope this helps - mm -----Original Message----- From: Dave Comeau [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 16, 2006 9:45 AM To: 'Maven Users List' Subject: RE: Help: Going crazy...antrun plugin dependencies issue For thread/arhive reference...I figured out my mistake when I started stripping down my pom. I defined the Antrun plugin again (for creating a custom jar in package phase) in the pom.xml, but it didn't have the dependency defined. So I guess the plugin's <dependencies> collection is reset. However, since I was able to execute my tasks in the first instance of the plugin, I guess the <executions> collection is appended? Seems like an honest mistake. Wish I'd been able to catch it sooner though. -----Original Message----- From: Dave Comeau Sent: Tuesday, August 15, 2006 1:29 PM To: 'Maven list ([email protected])' Subject: Help: Going crazy...antrun plugin dependencies issue I'm working on my first major M2 (v. 2.0.4) project in my spare cycles, and my obfuscation step was working fine last week. Now it's failing with a "can't find ant task" error, which seems like a classpath/dependency issue. I've tried everything I could think of, I'm hoping someone can point out my problem. It's possible I changed something by accident, but I can't see it. Does anyone a problem with this setup? ... <snip/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
