Hmmm, I seem to have egg on my face, I think that was my doing with
commons. Fine then, no src-deps.
On 8/9/2016 4:39 AM, Heiko W.Rupp wrote:
On 3 Aug 2016, at 15:25, Jay Shaughnessy wrote:
> responsibility. If you are responsible for the src-dep being in master
> then you are responsible for ensuring it doesn't block the release. So,
> by Friday, or Monday at the latest, either get rid of it yourself by
> doing a release of the component and updating the pom, or, find someone
And todays release build showed that this is not feasible,
as a src-dep indeed remained in master and broke the
release build.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev