TED]" <[EMAIL PROTECTED]>
> To: java-dev@lucene.apache.org
> Sent: Friday, May 9, 2008 8:06:06 AM
> Subject: Re: Lingustically-enhanced indexing for Lucene
>
>
> A couple of moths ago I asked in this list how to contribute to Lucene. You
> told
> me that I sh
Steven A Rowe wrote:
Hi Felipe,
On 05/09/2008 at 8:06 AM, [EMAIL PROTECTED] wrote:
On the other hand, it is java 1.5 compatible. Even
developments in contrib, that are rather independent,
must be java 1.4 compatible?
Actually, the policy is now that code in contrib can be java 1.5 (o
Hi Felipe,
On 05/09/2008 at 8:06 AM, [EMAIL PROTECTED] wrote:
> A couple of moths ago I asked in this list how to contribute
> to Lucene. You told me that I should do a patch a report a
> bug to JIRA. Actually, what I want to contribute is a
> completely new development that I think should be pla
On May 9, 2008, at 8:06 AM, [EMAIL PROTECTED] wrote:
On the other hand, it is java 1.5 compatible. Even developments in
contrib, that
are rather independent, must be java 1.4 compatible?
Java 5 is fine for contrib.
-
A couple of moths ago I asked in this list how to contribute to Lucene. You told
me that I should do a patch a report a bug to JIRA. Actually, what I want to
contribute is a completely new development that I think should be placed in the
contrib folder. It is not a bug, all the code is new, no exi
> > I am very interested in Apertium, especially if it is possible to
> > grow it for biblical Greek and Hebrew.
> >
> > Licensing threads seem to generate more heat than light. I hope that
> > my question won't. I develop code under many different licenses
> > including GPL, and feel that f
This question is probably best asked of the Apertium folks or asking a
lawyer (sorry!) or reading some of the millions of opinions out there
on licensing...
On Feb 13, 2008, at 8:29 AM, DM Smith wrote:
I am very interested in Apertium, especially if it is possible to
grow it for biblical
I am very interested in Apertium, especially if it is possible to grow
it for biblical Greek and Hebrew.
Licensing threads seem to generate more heat than light. I hope that
my question won't. I develop code under many different licenses
including GPL, and feel that following licenses prope
OK, we'll have to see the patch. Don't you just love licensing? :-)
-Grant
On Feb 13, 2008, at 3:49 AM, [EMAIL PROTECTED] wrote:
Apertium is licensed under the GNU GPL license version 2.
OK, this means that the Jars can not be included in the contrib. The
way to handle this is to have t
> >
> > Apertium is licensed under the GNU GPL license version 2.
>
> OK, this means that the Jars can not be included in the contrib. The
> way to handle this is to have the build script download them for the
> user. See the contrib/db module for how it handles the Berkeley
> database.
>
On Feb 12, 2008, at 9:47 AM, [EMAIL PROTECTED] wrote:
The best way to do this is to create a patch and attach it to a JIRA
issue. http://wiki.apache.org/lucene-java/HowToContribute has the
details.
Ok, I will read it. Thanks
Sounds like an interesting project. What are the licensing ter
> The best way to do this is to create a patch and attach it to a JIRA
> issue. http://wiki.apache.org/lucene-java/HowToContribute has the
> details.
Ok, I will read it. Thanks
>
> Sounds like an interesting project. What are the licensing terms for
> Apertium? On a side note, you might
The best way to do this is to create a patch and attach it to a JIRA
issue. http://wiki.apache.org/lucene-java/HowToContribute has the
details.
Sounds like an interesting project. What are the licensing terms for
Apertium? On a side note, you might be interested in Mahout (http://lucene.
13 matches
Mail list logo
