If you have a project which includes overridden jar files, furthermore, jar files who's location was overriden using the 'maven.jar.override=on' mechanism, it doesn't appear that they get included in the 'deploy:copy-deps' task.

Is there currently any way to patch this jelly script to do this, or even provide an alternative to accomplish the same type of thing?


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to