Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [birt-dev] Release Review

Hi Wim.

When you say "...without taking copyrights into consideration", do you really mean "...without taking licenses into consideration", or do you really mean copyrights?

Regarding the dependencies. I've actually been running the Eclipse Dash License Tool periodically on the pom.xml file in the root of the master branch in the Eclipse BIRT repository. AFAICT, all of the third-party content is correctly accounted for. Assuming that I'm looking in the right place and that the Maven dependency chain is accurate (i.e., there are no libraries hidden in bundles or some such thing), I believe that we're good to go.

Can you confidently state that the output from "mvn dependency:tree" accurately reflects the third party content that is included in the builds?

Have I correctly assumed that the master branch is up to date?


On Mon, Jan 31, 2022 at 9:33 AM Wim Jongman <wim.jongman@xxxxxxxxx> wrote:

We have been upgrading dependencies without taking copyrights into consideration.

I guess we can't release without having an ok for all dependencies. Do you have any advice on how this can be done the quickest?


birt-dev mailing list
To unsubscribe from this list, visit


Wayne Beaton

Director of Open Source Projects | Eclipse Foundation

Back to the top