You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Antoine Levy-Lambert <le...@tiscali-dsl.de> on 2003/01/30 11:50:13 UTC
Re: SSH Tasks
Having a SSH task in an is something that a lot of people are after.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13605
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16499
A lot of companies are banning telnet, ftp, rsh and rlogin from their
systems, to use only ssh, scp, sftp
Which licenses are acceptable for jar files or binary libraries required by
optional tasks ?
Finding a solution for a ssh task which would be part of ant, rather than
part of an extra SourceForge project would make things easier.
Ant users prefer to have a minimum of downloads to do to get their
environment setup; further there is always a danger that SourceForge
projects lose compatibility with new versions of ant.
If the mindterm license is not OK for inclusion in ant, there are two other
possibilities :
- finding another library with an Apache compatible license to do the
ssh connection (ideas ???)
- that the Ant PMC contacts mindterm and asks the company to release the
code required by the task developed by Rob Anderson under an acceptable
license for inclusion in ant
By the way, there are a number of tasks which are dependent on commercial
jar files, for instance the Visual Age tasks. Some tasks can only be
executed with commercial binaries (Perforce tasks for instance). So is there
a special problem for these ssh tasks, or is the ant PMC now more rigorous ?
Antoine
----- Original Message -----
From: "Steve Loughran" <st...@iseran.com>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Tuesday, November 26, 2002 9:16 PM
Subject: Re: SSH Tasks
>
> ----- Original Message -----
> From: "Anderson, Rob H - VSCM" <An...@vectorscm.com>
> To: <an...@jakarta.apache.org>
> Sent: Tuesday, November 26, 2002 10:37
> Subject: SSH Tasks
>
>
> > I have been working on an SSH task (attached) that will allow you to run
a
> > command remotely via ssh2. It will authenticate with an ssh key and
> > passphrase. It will only work if you have setup the authorized_keys on
the
> > remote host and can authenticate non-interactively when your key is
> loaded.
> > It relies on the mindterm classes
> > (http://www.appgate.com/mindterm/download.php).
>
> > I have a question about the licensing of such a task. Can I release it
> under
> > the Apache Software License? I am also planning to write a much needed
SCP
> > task. Please contact me with any questions and feedback. Thanks.
>
> You are constrained to release it under a licence that is compatible with
> the mindterm license, which looks GPL-ish, but I'd need to read more. If
it
> is GPL then you can only release your app under GPL too.
>
> This does not reduce the value of the submission, but prevents it ever
going
> into the apache codebase. My recommendation is to start a project on
> sourceforge and we can link to it from the ant docs/web site.
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Stefan Bodewig" <bo...@apache.org>
To: <an...@jakarta.apache.org>
Sent: Monday, February 10, 2003 01:47
Subject: Re: SSH Tasks
> On Fri, 7 Feb 2003, Steve Loughran <st...@iseran.com> wrote:
>
> > Though we do end up sporadically getting support calls related to
> > some random variant (like the Sun JWSDP version), that we have to
> > field, often by denying all knowledge :)
>
> 8-)
>
> Just one thing to clarify here. AFAIK JSWDP would have shipped a
> non-modified version of Ant if Ant 1.5 had been released in time for
> Sun's release plans. They wanted to have the JDK 1.4/WinXP Bug fixed,
> so they couldn't ship with stock Ant 1.4.1.
>
> Stefan
>
I was actually thinking of a recent bugrep about changes in the .bat file
they supply; that kind of thing is almost version independent.
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 7 Feb 2003, Steve Loughran <st...@iseran.com> wrote:
> Though we do end up sporadically getting support calls related to
> some random variant (like the Sun JWSDP version), that we have to
> field, often by denying all knowledge :)
8-)
Just one thing to clarify here. AFAIK JSWDP would have shipped a
non-modified version of Ant if Ant 1.5 had been released in time for
Sun's release plans. They wanted to have the JDK 1.4/WinXP Bug fixed,
so they couldn't ship with stock Ant 1.4.1.
Stefan
Re: SSH Tasks
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Stefan Bodewig" <bo...@apache.org>
To: <an...@jakarta.apache.org>
Sent: Friday, February 07, 2003 01:11
Subject: Re: SSH Tasks
> Ant is under a BSDish license. There are people who redistribute our
> code, even in modified form, and do so using a commercial license. Is
> this a problem for us? We still have Ant under our license, we don't
> get access to the modifications others have made, but this is their
> choice IMHO. Furthermore "they" are forced to give credit to us and
> must not call their product Ant.
Though we do end up sporadically getting support calls related to some
random variant (like the Sun JWSDP version), that we have to field, often by
denying all knowledge :)
Re: SSH Tasks
Posted by Dale Anson <da...@germane-software.com>.
Stefan Bodewig wrote:
>On Fri, 07 Feb 2003, Dale Anson <da...@germane-software.com> wrote:
>
>
>>Stefan Bodewig wrote:
>>
>>
>>
>>>On Thu, 06 Feb 2003, Dale Anson <da...@germane-software.com> wrote:
>>>
>>>
>>>
>>>>I wrote an ssh and scp task last month
>>>>
>>>>
>>>Any pointers to it? Your task, I mean.
>>>
>>>
>>>
>>It's at http://sourceforge.net/projects/antelope,
>>
>>
>
>Do you feel like putting together a blurb for our "related projects"
>page for Anteleope?
>
That's been on my "to do" list for the longest!
>
>
>
>>These are (IMHO) a decent start, but need some work, in particular
>>the ability to include filesets in the scp task.
>>
>>
>
>Hmm, even if jsch doesn't change its license, they could as well be a
>start of a task hosted by jsch - unless you really wanted them to
>remain part of Antelope.
>
The ssh tasks are packaged separately, they are not part of Antelope. My
thought is that they are useful on their own, so there is no reliance on
Antelope code to make them run. The only connection to Antelope is in
the package name, which, since it's all open source, can be changed if
anyone wants to.
>
>If an ssh task is part of Ant or the library it requires, the user
>will only have to download two things. Scattering Ant, the library
>and the task into three downloads will make it less attractive. But
>then again users are really in a need for these tasks, so they may be
>willing do that anyway 8-).
>
>
>
>>I'll forward your complete message to him and see where it goes.
>>
>>
>
>I've subscribed to the jsch-users list and will jump in if anything
>comes up.
>
>Stefan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 07 Feb 2003, Dale Anson <da...@germane-software.com> wrote:
> Stefan Bodewig wrote:
>
>>On Thu, 06 Feb 2003, Dale Anson <da...@germane-software.com> wrote:
>>
>>>I wrote an ssh and scp task last month
>>
>>Any pointers to it? Your task, I mean.
>>
> It's at http://sourceforge.net/projects/antelope,
Do you feel like putting together a blurb for our "related projects"
page for Anteleope?
> These are (IMHO) a decent start, but need some work, in particular
> the ability to include filesets in the scp task.
Hmm, even if jsch doesn't change its license, they could as well be a
start of a task hosted by jsch - unless you really wanted them to
remain part of Antelope.
If an ssh task is part of Ant or the library it requires, the user
will only have to download two things. Scattering Ant, the library
and the task into three downloads will make it less attractive. But
then again users are really in a need for these tasks, so they may be
willing do that anyway 8-).
> I'll forward your complete message to him and see where it goes.
I've subscribed to the jsch-users list and will jump in if anything
comes up.
Stefan
Re: SSH Tasks
Posted by Dale Anson <da...@germane-software.com>.
Stefan Bodewig wrote:
>On Thu, 06 Feb 2003, Dale Anson <da...@germane-software.com> wrote:
>
>>I wrote an ssh and scp task last month based on the jsch library
>>(java secure channel), which is currently LGPL'd.
>>
>
>Any pointers to it? Your task, I mean.
>
It's at http://sourceforge.net/projects/antelope, the ssh tasks are in a
separate file (follow the 'download' link), then get ssh_tasks_021.zip.
The zip has the source, docs, and compiled classes. I packaged them
separately because of the license issues...! These are (IMHO) a decent
start, but need some work, in particular the ability to include filesets
in the scp task.
>
>What can we do to address this concern?
>
I'll forward your complete message to him and see where it goes.
>
>Ant is under a BSDish license. There are people who redistribute our
>code, even in modified form, and do so using a commercial license. Is
>this a problem for us? We still have Ant under our license, we don't
>get access to the modifications others have made, but this is their
>choice IMHO. Furthermore "they" are forced to give credit to us and
>must not call their product Ant.
>
>If you need help in evangelizing, I'm here 8-)
>
Thanks! I've done a lot at work to get rid of shell scripts, python
scripts, perl scripts, dos batch files, etc, to replace them with pure
Ant. Unfortunately, there are still a few things missing, ssh/scp being
a key piece.
>
>Stefan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: ant-dev-help@jakarta.apache.org
>
>
>
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 06 Feb 2003, Dale Anson <da...@germane-software.com> wrote:
> So a BSD license would be acceptable?
Certainly.
> I wrote an ssh and scp task last month based on the jsch library
> (java secure channel), which is currently LGPL'd.
Any pointers to it? Your task, I mean.
> I've been talking with the library author about changing the
> license, and it appears he may be agreeable to a BSD license.
Cool. This would be extremely useful.
> His concern in changing licenses is that he doesn't want to see the
> library go the way of MindTerm, which originally was GPL, then
> changed to proprietary.
What can we do to address this concern?
Ant is under a BSDish license. There are people who redistribute our
code, even in modified form, and do so using a commercial license. Is
this a problem for us? We still have Ant under our license, we don't
get access to the modifications others have made, but this is their
choice IMHO. Furthermore "they" are forced to give credit to us and
must not call their product Ant.
If you need help in evangelizing, I'm here 8-)
Stefan
Re: SSH Tasks
Posted by Dale Anson <da...@germane-software.com>.
So a BSD license would be acceptable? I wrote an ssh and scp task last
month based on the jsch library (java secure channel), which is
currently LGPL'd. I've been talking with the library author about
changing the license, and it appears he may be agreeable to a BSD
license. His concern in changing licenses is that he doesn't want to see
the library go the way of MindTerm, which originally was GPL, then
changed to proprietary. The jsch library is at www.jcraft.com.
Dale Anson
danson@germane-software.com
Stefan Bodewig wrote:
>On 30 Jan 2003, Stefan Bodewig <bo...@apache.org> wrote:
>
>
>
>>IIRC there has been somebody working on a BSD licensed library at
>>sourceforge. Can't remember its name, but it must be in the
>>archives (ant-user, again IIRC).
>>
>>
>
><http://quietcoffee.sourceforge.net/> is what I've been looking for,
>seems to have slowed down, though.
>
>Stefan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: ant-dev-help@jakarta.apache.org
>
>
>
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On 30 Jan 2003, Stefan Bodewig <bo...@apache.org> wrote:
> IIRC there has been somebody working on a BSD licensed library at
> sourceforge. Can't remember its name, but it must be in the
> archives (ant-user, again IIRC).
<http://quietcoffee.sourceforge.net/> is what I've been looking for,
seems to have slowed down, though.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Antoine Levy-Lambert wrote:
> I do not understand why we have problems with GNU Licenses, and at the same
> time, we have for instance Visual Age tasks in ant.
In essence, the GNU license says that all code that uses GNU code, has
to be GNU code. This is not said in the Visual Age license.
...
> Concerning the SSH task, we need to find a supporting Java library
> containing SSH client functionality, on which we can base an ant ssh task.
> The ssh library itself does not have to be included in the ant distribution,
> leaving it to the users of ant to cope with downloading the ssh library from
> SourceForge and putting it under $ANT_HOME/lib on their machines.
Ant code would use that library. The Jar is not the only problem, it's
also its usage done in the Ant codebase.
> Antoine
>
> Here is a message from Lee David Painter, one of the authors of the J2SSH
> library
>
>
>>>Hi Antoine,
...
>>>If the ant project was to use our standard distribution there would be no
>>>licensing conflict due to the non infectious nature of the LGPL.
This is his own opinion. The fact is that it's not clear for Java
language, where "linking" is not defined, so we have decided to not risk.
Anyway, the decision is for the Ant PMC and ultimately the Apache board.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
wrote:
> I do not understand why we have problems with GNU Licenses, and at
> the same time, we have for instance Visual Age tasks in ant.
GPL forces any code that uses a GPL license to be distributed under
the GPL as well. This means, it is not distributed under our license,
so we won't distribute it.
> Is there any agreement between IBM and the Apache Software
> Foundation, allowing the ASF to distribute code which uses the
> Visual Age API ?
IBM allows anybody to distribute code that uses their API under any
license - at least that's my understanding.
> Concerning the SSH task, we need to find a supporting Java library
> containing SSH client functionality, on which we can base an ant ssh
> task.
If we want to distribute that task ourselves, yes.
> The ssh library itself does not have to be included in the ant
> distribution, leaving it to the users of ant to cope with
> downloading the ssh library from SourceForge and putting it under
> $ANT_HOME/lib on their machines.
Correct.
>>>If the ant project was to use our standard distribution there would
>>>be no licensing conflict due to the non infectious nature of the
>>>LGPL.
As I said, it depends on whom you ask. He seems to be in the "LGPL is
not infective, even if we are talking about Java" camp. Others have
different things to say.
Of course, the people who create the code are free to grant different
rights to different users. If all the J2SSH authors agree that it is
OK to write BSDish code (the Apache license is a BSD license after
all), against their library and state that publically, there'd be less
trouble for us.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Antoine Levy-Lambert <le...@tiscali-dsl.de>.
I do not understand why we have problems with GNU Licenses, and at the same
time, we have for instance Visual Age tasks in ant.
Is there any agreement between IBM and the Apache Software Foundation,
allowing the ASF to distribute code which uses the Visual Age API ? Is the
ant license "contaminated" by the commercial license of Visual Age ?
Concerning the SSH task, we need to find a supporting Java library
containing SSH client functionality, on which we can base an ant ssh task.
The ssh library itself does not have to be included in the ant distribution,
leaving it to the users of ant to cope with downloading the ssh library from
SourceForge and putting it under $ANT_HOME/lib on their machines.
Antoine
Here is a message from Lee David Painter, one of the authors of the J2SSH
library
>>Hi Antoine,
>>We would welcome the use of our J2SSH library in an SSH ant task. We
cannot
>>however change our license, as a great deal of time was spent evaluating
the
>>benefits of each open source license and it has been decided that the
Lesser
>>General Public License best suits our needs . This license has been chosen
>>to protect our investment of time in to the project and to ensure that any
>>derivitive versions would be also placed under an open source license, a
>>protection that the BSD license does not provide.
>>If the ant project was to use our standard distribution there would be no
>>licensing conflict due to the non infectious nature of the LGPL.
>>Regards
>>Lee
----- Original Message -----
From: "Nicola Ken Barozzi" <ni...@apache.org>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Thursday, January 30, 2003 2:50 PM
Subject: Re: SSH Tasks
> Stefan Bodewig wrote:
> > On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
> > wrote:
> >
> >>What does this mean in clear text ?
> >
> >>>There is no definitive answer here.
> >
> > Whether LGPL is OK or not to depend upon in ASF code depends on whom
> > you ask - even among board members.
> >
> > For me that is enough to keep away from it.
>
> Stefano Mazzocchi has been quite clear in this recent mail posted to
> cocoon-dev and licensing@apache.org:
>
> "
> Please understand that the recursive nature of the GPL license makes it
> impossible for any Apache licenced code to link to GPL code because the
> GPL doesn't protect the Apache brands (so it wouldn't comply to the
> Apache License requirements) and doesn't allow other licenses to further
> restrict the freedom the GPL gives.
>
> For LGPL licensed code, it would seem to be fair to link to it, but
> given the nature of the Java language, there is no way to tell where the
> 'library' stops and where your program starts.
>
> To avoid potential legal troubles, the Cocoon project, according to a
> ASF-wide policy created by the Apache Licensing Committee, prefers to
> avoid hosting and distributing any code that links to LGPL code because
> that might force the entire code to be released as LGPL, thus
> conflicting with the Apache license requirements of brand protection.
>
> Also note that moch classes and interfaces don't solve the issue since
> they could be considered a derivative work of the LGPL library, thus
> would need to be LGPL-ed as well.
> "
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ant-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Stefan Bodewig wrote:
> On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
> wrote:
>
>>What does this mean in clear text ?
>
>>>There is no definitive answer here.
>
> Whether LGPL is OK or not to depend upon in ASF code depends on whom
> you ask - even among board members.
>
> For me that is enough to keep away from it.
Stefano Mazzocchi has been quite clear in this recent mail posted to
cocoon-dev and licensing@apache.org:
"
Please understand that the recursive nature of the GPL license makes it
impossible for any Apache licenced code to link to GPL code because the
GPL doesn't protect the Apache brands (so it wouldn't comply to the
Apache License requirements) and doesn't allow other licenses to further
restrict the freedom the GPL gives.
For LGPL licensed code, it would seem to be fair to link to it, but
given the nature of the Java language, there is no way to tell where the
'library' stops and where your program starts.
To avoid potential legal troubles, the Cocoon project, according to a
ASF-wide policy created by the Apache Licensing Committee, prefers to
avoid hosting and distributing any code that links to LGPL code because
that might force the entire code to be released as LGPL, thus
conflicting with the Apache license requirements of brand protection.
Also note that moch classes and interfaces don't solve the issue since
they could be considered a derivative work of the LGPL library, thus
would need to be LGPL-ed as well.
"
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
wrote:
> What does this mean in clear text ?
>> There is no definitive answer here.
Whether LGPL is OK or not to depend upon in ASF code depends on whom
you ask - even among board members.
For me that is enough to keep away from it.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Antoine Levy-Lambert <le...@tiscali-dsl.de>.
What does this mean in clear text ?
Is there a legal guru who could help, before development efforts get wasted
?
Antoine
----- Original Message -----
From: "Stefan Bodewig" <bo...@apache.org>
To: <an...@jakarta.apache.org>
Sent: Thursday, January 30, 2003 12:50 PM
Subject: Re: SSH Tasks
> On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
> wrote:
>
> > Is the ssh library described under this URL
> > http://sourceforge.net/projects/sshtools/ more suitable from a
> > licensing point of view to base an ant ssh task on ?
>
> Ahh, the difficult realms of LGPL. There is no definitive answer
> here.
>
> If you read the LGPL you will notice that the language is very
> focussed on languages with an explicit linking semantic (like C) and
> that much of it doesn't really apply to Java.
>
> In fact, some people (of the FSF) have indicated that the LGPL would
> be equivalent to the GPL when it comes to Java - sorry, no references
> here.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ant-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
wrote:
> Is the ssh library described under this URL
> http://sourceforge.net/projects/sshtools/ more suitable from a
> licensing point of view to base an ant ssh task on ?
Ahh, the difficult realms of LGPL. There is no definitive answer
here.
If you read the LGPL you will notice that the language is very
focussed on languages with an explicit linking semantic (like C) and
that much of it doesn't really apply to Java.
In fact, some people (of the FSF) have indicated that the LGPL would
be equivalent to the GPL when it comes to Java - sorry, no references
here.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
Antoine Levy-Lambert wrote:
> I do not understand why we have problems with GNU Licenses, and at the same
> time, we have for instance Visual Age tasks in ant.
It's funny isn't it. IANAL, but IMHO, the problem arises when you link to
the GNU code. This places obligations on you with regard to your code. Since
the FSF considers the Apache licence unsuitable, we cannot meet those
obligations Commercial licences, in general, do not place obligations on
your code, they mostly deal with what you can do with their code (binary).
This is the "viral" nature of GNU licences.
> Here is a message from Lee David Painter, one of the authors of the J2SSH
> library
Well, as Stefan has said, not everyone in the FSF agrees and there is a
suggestion that for Java effectively LGPL = GPL. It comes down to what you
understand by the term "linking". I think perhaps this is the difficult
clause in the LGPL
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
It's obviously C-think (header files, object code) and interpreting this
already imprecise clause in Java context is pretty difficult - hence
consensus at Apache is that it is safer not to use LGPL.
Perhaps the best hope would be for them to distribute an Ant SSH task with
their SSH code - not sure if this violates the LGPL or not.
Conor
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Antoine Levy-Lambert <le...@tiscali-dsl.de>.
Stefan Bodewig wrote :
> IIRC there has been somebody working on a BSD licensed library at
> sourceforge. Can't remember its name, but it must be in the archives
> (ant-user, again IIRC).
>
Is the ssh library described under this URL
http://sourceforge.net/projects/sshtools/ more suitable from a licensing
point of view to base an ant ssh task on ?
Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org
Re: SSH Tasks
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 30 Jan 2003, Antoine Levy-Lambert <le...@tiscali-dsl.de>
wrote:
> Which licenses are acceptable for jar files or binary libraries
> required by optional tasks ?
Depends on how and where the optional tasks are distributed.
Optional tasks that are part of Ant must be themselves licensed under
the Apache Software Foundation license. If the library you want to
use allows you to write code that is licensed under the ASF license,
it is OK. The GPL does not allow us to do so.
If you distribute optional tasks yourself, you are free to pick
whatever license you please - and therefore may be able to use a
matching library. Note that importing Ant's Task class may make your
code violate the GPL (from the GPL's point of view) so this is pretty
much not an option there either, from a legal standpoint.
> Finding a solution for a ssh task which would be part of ant, rather
> than part of an extra SourceForge project would make things easier.
I agree.
> - finding another library with an Apache compatible license to do
> the ssh connection (ideas ???)
IIRC there has been somebody working on a BSD licensed library at
sourceforge. Can't remember its name, but it must be in the archives
(ant-user, again IIRC).
> By the way, there are a number of tasks which are dependent on
> commercial jar files,
This is no problem, as long as the license of these libraries enables
us to distribute the tasks - not the library itself, we don't do that.
> So is there a special problem for these ssh tasks, or is the ant PMC
> now more rigorous ?
This page here <http://www.appgate.com/mindterm/licensing.php> doesn't
indicate which license would apply if I want to distribute an
application that uses mindterm, but don't distribute mindterm itself.
"compiling any data or information using the Licensed Products" falls
under "usage" in all their licenses, as well as "storing". From my
(IANAL and all that) interpretation of this: anybody having the source
code to a task that uses the library on his/her disk, needs to comply
to one of their licenses.
This doesn't give me a warm and cozy feeling and without any written
consent of appgate, that the ASF is free to use the library in any way
it wants, I'd stay away from this code.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org