Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362646 - Clarify licensing situation in org.eclipse.jetty.toolchain
Summary: Clarify licensing situation in org.eclipse.jetty.toolchain
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: documentation (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 7.5.x   Edit
Assignee: Shirley Boulay CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 05:17 EDT by Stanislav Ochotnicky CLA
Modified: 2012-01-12 05:10 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Ochotnicky CLA 2011-11-02 05:17:54 EDT 
Build Identifier: 

Neither git repository nor tarballs (created from repository) contain any licensing information. I would assume ASL 2.0/EPL 1.0 multi-licensing scenario similar to jetty-project, but better safe than sorry...

Reproducible: Always
Comment 1 Alexander Kurtakov CLA 2012-01-11 07:20:59 EST 
Seems to be fixed with http://git.eclipse.org/c/jetty/org.eclipse.jetty.toolchain.git/commit/?id=722131aae94200f9f021cb977b49e971009c3f78 .
Should this be closed now?
Comment 2 Stanislav Ochotnicky CLA 2012-01-12 05:10:15 EST 
True, those commits are enough from my POV. Thanks, closing.