|
0
|
1 |
License
|
|
|
2 |
|
|
|
3 |
The CLucene Core Library uses a dual license strategy for the source code.
|
|
|
4 |
These licenses are the GNU Lesser General Public License (LGPL) and the Apache
|
|
|
5 |
License (Version 2.0). Users can choose the license they wish to distribute
|
|
|
6 |
their software under. This means that you do not need to abide by *both*
|
|
|
7 |
licenses, but rather than you can choose the license which most suits your
|
|
|
8 |
needs.
|
|
|
9 |
|
|
|
10 |
To rephrase this and to make it perfectly clear:
|
|
|
11 |
CLucene is distributed under the GNU Lesser General Public License (LGPL)
|
|
|
12 |
*or*
|
|
|
13 |
the Apache License, Version 2.0
|
|
|
14 |
|
|
|
15 |
However, we are an open source project, and we encourage users to use the LGPL
|
|
|
16 |
license and participate fully in the free software community. Dual licensing
|
|
|
17 |
of the CLucene source code provides open and free access to the technology both
|
|
|
18 |
for the GPL community and for other developers or companies that cannot use the
|
|
|
19 |
GPL.
|
|
|
20 |
|
|
|
21 |
You can freely modify, extend, and improve the CLucene source code. The only
|
|
|
22 |
question is whether or not you must provide the source code and contribute
|
|
|
23 |
modifications to the community. The GNU and Apache licenses allow different
|
|
|
24 |
ranges of flexibility in this regard, but in the end, regardless of the license
|
|
|
25 |
used, we highly recommend that you submit any bugs, incompatibilities or
|
|
|
26 |
added features.
|
|
|
27 |
|
|
|
28 |
Note that this same license does *not* apply to the CLucene Contributions
|
|
|
29 |
package. You should read the COPYING file in that directory or package for
|
|
|
30 |
more information. |