Thanks for taking the time to reply. Your comments are encouraging.
I think a document that clearly states how this impacts Subclipse and
svnClientAdapter would be great. Let me restate some of the things I
think you are saying.
1) Let's say IBM wants to include Subclipse with all of their Rational
distributions. As long as they are just including the plugin the same way
we distribute it then there are no issues and no JavaSVN license is
2) Let's say that IBM includes Subclipse but they have modified parts of
it, like some of our dialogs. Or maybe they have added some other feature
a) If the modifications they make to Subclipse are available via open
source, then they do not need a license for JavaSVN.
b) If the modifications are not made available, then they would either
require a license for JavaSVN (or remove it as part of their
3) If Subclipse someday provides extensions points for additional
functionality, then commercial closed-source plugins can use those
extension points without requiring a JavaSVN license, provided of course
that they are using the standard Subclipse install in the first place.
4) Anyone using svnClientAdapter in internal projects do not require a
license because they are not making the results of that work available to
others as part of any kind of commercial enterprise?
These things all seem reasonable.
Assuming these issues are worked out, the other thing to talk about are
the changes you feel we need to make in Subclipse (and svnClientAdapter
and svnAnt) to be compliant with the terms of your license. For example,
we do not ship the source code as part of the normal plugin distribution
and while we can certainly distribute your license agreement and other
items like that, as you are probably aware these items are far from
visible in the Eclipse UI. The only visible place I can think of where we
could add the required attributions are in the click-thru license
agreement you get when you install a plugin.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Oct 22 01:19:36 2005