]
Lars Heinemann commented on JBIDE-24641:
----------------------------------------
As far as I remember the reason for putting the SAP tooling into a separate repo was that
we wanted to exclude code which makes use of non-opensource code. (means usage of classes
which are part of closed source libs like the SAP connector ones). The closed source
libraries are to be downloaded from the SAP customer account manually. I don't see
why we should add the SAP license text into our repo? We are just using their classes, we
are not providing their libraries.
update readme/license terms for Fuse Extras / SAP tooling
---------------------------------------------------------
Key: JBIDE-24641
URL:
https://issues.jboss.org/browse/JBIDE-24641
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build, fuse-tooling
Affects Versions: 4.5.0.AM2
Reporter: Nick Boldt
Assignee: Lars Heinemann
Fix For: 4.5.0.AM2
Had another look into the sources of
https://github.com/jbosstools/jbosstools-fuse-extras
and the ONLY license mention I see that isn't EPL is this:
{quote}
Copyright (C) 2010 FuseSource, Corp. All rights reserved.
http://fusesource.com
The software in this package is published under the terms of the AGPL license
a copy of which has been included with this distribution in the license.txt
file.{quote} --
https://github.com/jbosstools/jbosstools-fuse-extras/blob/master/pom.xml#...
But there's no license.txt file, and the LICENSE file is a copy of the EPL, not a
*GPL license.
So... can someone ( [~lhein] ? [~aurelien.pupier] ?) point me to where the non-EPL
sources actually are, or where non-EPL stuff is downloaded? If not, I'll update this
root pom to replace Copyright FuseSource with the usual Red Hat copyright 2017, with
FuseSource as an initial contributor.