Stefano Mazzocchi <[EMAIL PROTECTED]> writes:
...
> If you use *regular* programming practices you have to do
>
> import LGPLObject;
>
> then
>
> LGPLObject o = new LGPLObject();
> o.doSomething();
>
> that will
>
> 1) ask the classloader to find that object
> 2) allocate memory for
Stefano Mazzocchi wrote:
Santiago Gala wrote:
Stefano Mazzocchi wrote:
Morgan Delagrange wrote:
OK, Java-specific question. It seems likely that
altering or inlining LGPL code pollutes the Apache
license. Are you of the opinion that IMPORTING but
not altering or distributing LGPL classes pollutes
Santiago Gala wrote:
Stefano Mazzocchi wrote:
Morgan Delagrange wrote:
OK, Java-specific question. It seems likely that
altering or inlining LGPL code pollutes the Apache
license. Are you of the opinion that IMPORTING but
not altering or distributing LGPL classes pollutes the
Apache licecnse? An
Stefano Mazzocchi wrote:
Morgan Delagrange wrote:
OK, Java-specific question. It seems likely that
altering or inlining LGPL code pollutes the Apache
license. Are you of the opinion that IMPORTING but
not altering or distributing LGPL classes pollutes the
Apache licecnse? And if so, can that be
Morgan Delagrange wrote:
OK, Java-specific question. It seems likely that
altering or inlining LGPL code pollutes the Apache
license. Are you of the opinion that IMPORTING but
not altering or distributing LGPL classes pollutes the
Apache licecnse? And if so, can that be stated on the
Wiki page?
On 6/2/03 5:25, "Daniel Rall" wrote:
> Morgan Delagrange <[EMAIL PROTECTED]> writes:
>
>> Dang, I wish that archive was searchable. [wink, wink]
>
> Pier, the unix permissions on the Lucene index directory for
> community@apache.org don't allow writes by the unix user "apache"
> which Catalina
Justin Erenkrantz <[EMAIL PROTECTED]> writes:
> --On Wednesday, February 05, 2003 21:25:47 -0800 Daniel Rall
> wrote:
>
>
> > can't change /opt/tomcat/webapps/eyebrowse/index/apche.org/community
>
> Man, I hope our search engine doesn't index www.apche.org.
Heh, me too.
> I actually encounte
--On Wednesday, February 05, 2003 21:25:47 -0800 Daniel Rall
wrote:
can't change /opt/tomcat/webapps/eyebrowse/index/apche.org/community
Man, I hope our search engine doesn't index www.apche.org.
I actually encountered this site at ApacheCon while Brian and David were
running etherpeg. ;-) --
Morgan Delagrange <[EMAIL PROTECTED]> writes:
> Dang, I wish that archive was searchable. [wink, wink]
Pier, the unix permissions on the Lucene index directory for
community@apache.org don't allow writes by the unix user "apache"
which Catalina is running as:
[EMAIL PROTECTED]:dlr$ ls -lad
/op
Conor MacNeill <[EMAIL PROTECTED]> writes:
> Morgan Delagrange wrote:
> > OK, Java-specific question. It seems likely that
> > altering or inlining LGPL code pollutes the Apache
> > license. Are you of the opinion that IMPORTING but
> > not altering or distributing LGPL classes pollutes the
> >
> Ken, can we get this on the Wiki page to protect
> feeble-minded folks like me?
> http://nagoya.apache.org/wiki/apachewiki.cgi?Licensing
I had just finished doing that. I hope that I got them right.
--- Noel
-
To unsu
--- Conor MacNeill <[EMAIL PROTECTED]>
wrote:
> Morgan Delagrange wrote:
> > OK, Java-specific question. It seems likely that
> > altering or inlining LGPL code pollutes the Apache
> > license. Are you of the opinion that IMPORTING
> but
> > not altering or distributing LGPL classes pollutes
> t
Morgan Delagrange wrote:
OK, Java-specific question. It seems likely that
altering or inlining LGPL code pollutes the Apache
license. Are you of the opinion that IMPORTING but
not altering or distributing LGPL classes pollutes the
Apache licecnse? And if so, can that be stated on the
Wiki page?
13 matches
Mail list logo
