Submit your fixed Axis pom to JIRA, component MEV (Maven Evangelism) to get it updated in Central.
http://jira.codehaus.org Wayne On 5/12/06, David Smiley <[EMAIL PROTECTED]> wrote:
Hi. I'm trying to avoid specifying the list of dependencies that Axis requires in several of my modules. In an ideal world, Axis would have a proper POM (i.e. one that specifies its dependencies) and I wouldn't be trying to do this. I'll try to get that changed, but in the mean time I'd like to work around this somehow. I don't want to specify all of them in my parent module because not all of the modules need Axis. I thought perhaps I could create a module that is a POM of Axis' dependencies (packaging is pom), and then I could have an axis-using module depend on that pom. It didn't work; at the compilation phase of my axis-using module, Axis' dependencies weren't on the classpath. Previously I had to do a "mvn install" of the axis pom because the other module couldn't find it. Any ideas? ~ Dave Smiley --------------------------------------------------------------------- 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]
