package - should be simple but it ain't

[pdesalvia <pi...@gmail.com>]

Hello,

I'm trying to package a library we created, which has compile-time
dependencies on a few packages [spring and so forth], and it works fine
but...we don't want the dependencies in the final jar.

We have declared all dependencies to be either all provided or all compile,
either way they end up in the final jar when we issue "mvn package".

What's the secret?
-- 
View this message in context: http://www.nabble.com/package---should-be-simple-but-it-ain%27t-tp23883890p23883890.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: package - should be simple but it ain't

[Wayne Fay <wa...@gmail.com>]

> We have declared all dependencies to be either all provided or all compile,
> either way they end up in the final jar when we issue "mvn package".

"mvn clean package" to clean up target which is polluted with deps
from previous runs. In all likelihood, that will fix your issues.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org