From: David W. <dwi...@op...> - 2009-09-30 15:33:32
|
On Wed, 2009-09-30 at 17:13 +0200, Andrea Aime wrote: > Since the current web/app module is declared as a jar instead of a war > thought (custom packaging issues I guess) you'll have to find a way > not to depend on the .war or else see if you can make web/app build a > .war instead. Well, I tried just switching the packaging and running a test release yesterday and it seemed all right. However, we could also just use the deploy:deploy-file task and avoid messing with the current module setup. http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Though, I wonder whether it makes sense to deploy the same WAR to Maven that we publish on the download page. It seems likely that projects depending on the WAR will not need all the provided data that goes into the release on the download page. I will take a second, closer look at simply switching the web-app packaging over to WAR today. -- David Winslow OpenGeo - http://opengeo.org/ |