Hi Anders; and first, thanks a bunch for your comments, much appreciated. :)
Anders Hammar schrieb: > I think you should have scope 'provided'. Your use case is what that's for. Yes, that's what I thought as well, but, well, it's not always the case - we're using the same app code base for various deployments, but in not all situations the artifacts actually _are_ provided / to be placed in the server environment... And so far I hesitated having two different war artifacts just to address this issue... but maybe it would be a cleaner solution? > Regarding handling your dependencies for production, that's more of a server > deployment issue isn't it? What I think you can use is the copy-dependensies > mojo of the dependency plugin ( > http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html). > As the dependencies are shared between several applications, I would create > a separate project where I do this and the put them in an assembly (zip/tar > file). Thanks for pointing me there, taking a first look this seems pretty much what I need. I'll play around with it and see how far it gets me; at the moment, thanks a bunch again for your help. :) Cheers, Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
