Licenses reported improperly

Issue #93 resolved
Rafał Wrzeszcz created an issue

https://www.versioneye.com/user/projects/538b45046248d2175b000035 - project page claims there are 4 license whitelist violations, but after switching to Licenses tab there is nothing shown.

Although all of project pom.xmls have 0 licenses violations, in root pom.xml 0 is marked red.

Comments (5)

  1. Robert Reiz

    @rafalwrzeszcz It's fixed now. See here. The problem was that the license whitelist was not assigned to all sub projects. On of them was without license whitelist.

    Can you tell me a bit more about how you created the project(s), how you merged them and at which time you assigned the license whitelist to the project? That would help me to re produce the situation.

  2. Rafał Wrzeszcz reporter

    I think the project was created (top level one) before submodule projects feature was introduced into VersionEye. After that (when submodules were implemented in VE), when I've found some time, I created subprojects and merged them into parent one.

    I'm not sure about assigning whitelist - I think I have my "Open Source" whitelist set as default and all other sub-modules have received it as initial whitelist... But maybe I just changed it by misstake and didn't notice. Thanks for the reply.

  3. Robert Reiz

    OK. That helps me. I just double checked the code and did some changes. Now the license whitelist from the parent project gets assigned to the child projects on each project update.

    Let me know if you find something else.

  4. Log in to comment