Re: [Hawkular-dev] When to remove snapshots maven repo from parent? --> Integration tests

This is a different debate than SNAPSHOT repo in/out the parent, but this is IMO important: On 06/01/2015 03:46 PM, Lucas Ponce wrote: As I said, this is incorrect, you shouldn't create such dependency circles even for tests. And as a matter of fact Alerts has tagged releases with dependencies on a SNAPSHOT https://github.com/hawkular/hawkular-alerts/blob/0.0.4/pom.xml The release plugin should have complained. The only certitude is that *at the point of the release* the tests passed, Hawkular may still change and by the time Hawkular is released with that version of Alerts it may fail the same integration tests -> Bad This is the minimum you can do to have a proper release: 1 - release alerts, make sure they pass the unit tests 2 - upgrade hawkular to use that version of alerts 3 - release hawkular with the integration tests, if they fail at this point you may need to re-release alerts but at least you know for sure that the integration tests passed when you did the release. There are several improvements that can be made that are more or less costly to avoid "wrong" release of components: - Before you tag alerts, I would recommend that you test Hawkular with a locally built SNAPSHOT of Alerts, that reduce the risk of a re-release of alerts - Do release:perform of the components and don't close on Nexus, upgrade hawkular to use the new tagged version (and add the staging repo in your local settings.xml) test, release Hawkular and close/publish all the Nexus repo "at once". (I think you can even do the release:prepare and not push the tag so that you can freely retag until the tests pass, and when you push the binaries you can also push the sources tags).