Hi,
> All, I'm not sure what the procedure here should be. Do we need to
> re-release 1.0.0 or is that horse gone, and we should release a fixed 1.0.1?
I would just fix it when you make a new release.
Thanks,
Justin
Thanks for pointing this out, Justin.
All, I'm not sure what the procedure here should be. Do we need to
re-release 1.0.0 or is that horse gone, and we should release a fixed 1.0.1?
Regards
Geoff
On Mon, 18 May 2020, 10:18 Aled Sage, wrote:
> Hi Justin,
>
> Thanks for spotting this and
iuliana opened a new pull request #1100:
URL: https://github.com/apache/brooklyn-server/pull/1100
Revert "Revert "This closes #830""
This reverts commit 4236ff272903a8ffe77a06d9b146aea40b3f057e.
This is an automated
Hi Justin,
Thanks for spotting this and reaching out.
Looking at the license/notice generation, I think there are two things
that went wrong for 1.0 release:
1. The maven license plugin [1] picked the wrong license for
dependencies when there were multiple to choose from (i.e. LGPL vs
