Hi, I am wondering what the recommended way is to deal with legacy dependencies (those that can not be resolved against an official repository) for artifacts that are going to be published to central.
The module in doubt is a showcase application (war) that belongs to a web interface integration library. The showcase web application needs a library which is sadly not published via central. Technically, it only needs to be moved to WEB-INF/lib for the resulting artifact. The most obvious solution would be to do this in the prepare-package phase e.g. with the dependency:copy goal. The dependency would then not be declared in the pom.xml, AFAICS Another way I could think of is performing an install:file goal in the initialize phase. This would allow me to declare the legacy lib as formal dependency in the applications's pom.xml. It would also be available in test phase then. My questions: 1. What is the recommended way to deal with this problem? 2. Are both solutions feasible, or are there any obligations for pushing to the app artifact to central that would not be met? 3. Are there other solutions I missed? TIA, - René -- René Gielen http://twitter.com/rgielen --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
