| Summary: | Upgrade API JGroups provider | ||
|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Pierre-Henry Perret <phperret> |
| Component: | ecf.providers | Assignee: | ecf.core-inbox <ecf.core-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | bugs.eclipse.org, wim.jongman |
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Pierre-Henry Perret
Does this need to become a CQ? No, it does not. jgroups lib is under the LGPL (In reply to comment #2) > No, it does not. > jgroups lib is under the LGPL Even if JGroups is licensed under LGPL you will have to file a CQ nonetheless. Unless there existing a CQ for JGroups 2.12 alerady ECF can piggyback on. No, it does not. jgroups lib is under the LGPL (In reply to comment #3) > (In reply to comment #2) > > No, it does not. > > jgroups lib is under the LGPL > > Even if JGroups is licensed under LGPL you will have to file a CQ nonetheless. > Unless there existing a CQ for JGroups 2.12 alerady ECF can piggyback on. Ok - It will be necessary for integration in ECF release which is not scheduled now. This integration needs to finalize the o.e.e.p.jgroups.ui see [0] [0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=221157 |