Of course snapshots would work for my scenario as well. I had
discounted the possibility but I guess it's a fair question for short
periods of time. As long as nothing blocks the weekly release it seems
reasonable. But i can also live with bunches of releases if we always
have people with privs to build each component. I know Lucas or I can
typically release Alerting.
On 8/2/2016 3:38 PM, Stefan Negrea wrote:
Hello,
I agree with the comments on the src-deps plugin. In fact I am in
favor of going on step further and rejecting PRs using it.
At the same time can we reinstate the use of SNAPSHOTs dependencies?
Thank you,
Stefan Negrea
On Tue, Aug 2, 2016 at 2:38 AM, Juraci Paixão Kröhling
<jpkroehling(a)redhat.com <mailto:jpkroehling@redhat.com>> wrote:
Team,
It seems there's a small confusion about src-deps and H-Services.
H-Services is a module that is released every week, given that there's
at least one new commit since the last release.
The src-deps plugin is very helpful for our daily work, as it
allows us
to use a given commit as a dependency for our modules, but it's not
appropriate for released artifacts, as it kinda breaks the stability
promise that "a released artifact uses only released artifacts"
that is
common on Maven. Besides, I believe there were problems in the past
between src-deps and the maven-release-plugin.
So, avoid sending PRs with src-deps to H-Services. If for some reason
you really need to, switch it to a proper version before Tuesday
morning.
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev