Closed rawlingsj closed 8 years ago
@rawlingsj it sounds strange to me since maven convention is to create packages during package
phase. I think I should be able to change it to install
, I'll do it today.
Do we have to do the same thing on the redhat
branch, or is it unrelated to the license signing on the master
branch?
@dhirajsb sorry I got my package / install comments back to front, it's currently at install
which causes the problem above, it's my best guess that the signing issue is because the karaf assembly should be at package
which it wasn't set at when added. From your comment above that convention is to create it at package maybe this is not much of an issue and needs changing along with addressing the integration test failure after doing so.
fixed thanks for sorting that @chirino
The quickstarts are now enabled which is causing an issue during the release as the license signing hasnt happened on the karaf quickstarts...
As far as I can tell this is because the karaf quickstarts build the zips and tar.gz in the package phase however the license signing needed by sonartype needs them to be created during install. https://github.com/fabric8io/ipaas-quickstarts/blob/master/quickstart/karaf/camel-amq/pom.xml#L246
I'm not sure of the impact of changing this to install but certainly the tests fail.
@chirino @dhirajsb I'll disable the quickstarts so that we can get this release out but could one of you look at the karaf examples so that the tarballs are created in the
install
phase so that the license signing takes place during the release? Then we can include the quickstarts again.