Bug 547592 - Remove cpl-v10.html from about files in org.junit 4.12
Summary: Remove cpl-v10.html from about files in org.junit 4.12
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-23 09:02 EDT by Bhuvaneswari Ethiraju CLA
Modified: 2023-05-14 15:03 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bhuvaneswari Ethiraju CLA 2019-05-23 09:02:26 EDT
org.junit_4.12.0.v201504281640 is integrated in Eclipse JDT.
This plugin has cpl-v10.html inside "org.junit_4.12.0.v201504281640\about_files"

From Junit 4.12, the licensing has been changed from cpl to epl.
Refer https://mvnrepository.com/artifact/junit/junit/4.12

The cpl license should be removed and epl license must be added inside "org.junit_4.12.0.v201504281640\about_files".

Kindly feedback on the above request.
Comment 1 Eclipse Genie CLA 2021-05-13 09:45:09 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-05-14 15:03:46 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.