Hi Guys I've written a plugin that creates a new packaging type which creates a *.zip and a *.jar artefacts. Dependencies of the same packaging type are deployed together.
The problem is that while the code is deployed together, adding this dependency to my POM means that the same JAR file is not added to the Maven classpath, so code fails unless I add the dependency twice, once as the new packaging type, and again as a JAR dependency in the "provided" scope. Is there anyway to automatically add dependencies to the Maven classpath so that when the java maven plugin executes they are available, and so that they don't have to be made explicit in the POM? Regards... -- Ricardo Gladwell <[email protected]> http://www.google.com/profiles/ricardo.gladwell Twitter: @rgladwell - MSN: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
