Need to acknowledge the same license twice when installing AWS Toolkit for Eclipse about aws-toolkit-eclipse

[fulghum]

This is an artifact of some third-party code (json.org) that's embedded in the AWS SDK for Java. The second Apache license file actually has an attribution for the json.org code at the very end of the license. It's something we'd like to clean up in the AWS SDK for Java. We aren't using the json.org code for much anymore – we're almost exclusively using Jackson. I'll check in with the team and see how much code we have left depending on the json.org classes. We've been wanting to clean that up for a while; it just hasn't bubbled up to be a priority yet.

[shorea]

We dropped JSON.org in 1.11.0.

[fulghum]

Thanks for the update Andrew. Sounds like we just need to update the attribution in the SDK and get the latest version into the Eclipse Toolkit and this will go away.

[fulghum]

Actually... the plot is thickening on this one... we've removed json.org and it's attribution; it's not mentioned in the SDK's license file or in the Eclipse license file. @zhangzhx will dig in a little deeper and find out exactly what's different here and we'll get this cleaned up.

[zhangzhx]

The core plugin has some files under EPL 1.0. See here. We'll clean these files up. Thanks for the report.

[rherrmann]

To my knowledge, the different licenses of all features to be installed are listed in this context. Different, here, means that the text given in <license> element in the feature.xml differs - if only slightly.

A license feature may help here to avoid (slightly different) duplicates.

[zhangzhx]

I have rewritten the code under EPL and removed the EPL declaration. So the new version of the toolkit only has Apache license.