We're struggling to get this combination to work. We want to produce a WAR that gets packaged into an RPM. We then want the RPM pushed up to Nexus during our deploy phase. We're having a lot of trouble getting the two plugins to play nice together.
Our current attempt has the war plugin bound to the package phase and the rpm bound to the deploy phase. The rpm plugin has it's extensions enabled so that we can set <packaging>rpm</packaging>. What happens is that we run "mvn clean deploy" and the rpm fails because the war file never gets created. Our other configuration, which doesn't work either, is to use war as our packaging. We setup war as our packaging and let the war-plugin do it's thing. Then we bind the rpm:attached-rpm goal to the deploy phase. This all works in that a war is created and an RPM is created. But the RPM never gets deployed only the war file. Again, the end result we're hoping for is that an RPM of our WAR gets created and deployed to Nexus. Anyone have an idea? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
