wcmio-content-package-maven-plugin should fail if bundles are not up & running after 360 sec

i understand your use case, but consider following scenario where the current behavior makes sense:

• you have a deployment consisting of two packages A and B, both containing a couple of OSGi bundles

• B contains a bundle depending on a bundle from A with major version 1.0

• in a new deployment, the bundle in A is updated to 2.0, and the bundles in B are also recompiled to reference 2.x instead of 1.x from the A bundle

• in the usual order package A is redeployed before package B. but when package A is deployed, the existing bundles from package B cannot start, because the still reference version 1.0 from A (the updated package B is not yet deployed).

• this leads to the 360 sec delay, until the deployment continues and then package B is deployed and all is fine

i understand that this is a bit an edge case and does not happen that often - but it happens. we do not have a heuristic in place that automatically detects whether a failure after 360sec is really a failure, or only a temporarily one for an edge case as described above.

having said that, it still might make sense to introduce a new config parameter that allows to control the behavior whether to continue after the 360sec or fail the build, than every user can decide and probably switch it on only if such an edge case occurs.

do you want to come up with a PR?