You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by "Gregor J. Rothfuss" <gr...@apache.org> on 2005/01/20 05:19:32 UTC

why do we have our own lucene / log4j jars?

cocoon 2.1.6 has lucene 1.4.3 while we have a 1.4.1 jar in lenya.

same for log4j: we have 1.2.8, cocoon 2.1.6 has 1.2.9 in their core libs.

if i remember correctly, we have lucene because cocoon used to have 1.3, 
and log4j was not always included in a cocoon build. since both of these 
situations have changed, can we remove these libraries from lenya?

-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: why do we have our own lucene / log4j jars?

Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:

> cocoon 2.1.6 has lucene 1.4.3 while we have a 1.4.1 jar in lenya.
>
> same for log4j: we have 1.2.8, cocoon 2.1.6 has 1.2.9 in their core libs.
>
> if i remember correctly, we have lucene because cocoon used to have 1.3,


right, because Lucene 1.4 supports sorting and we were ahead of Cocoon.
Since Cocoon upgraded I guess we can remove it for the moment, but I 
wouldn't remove the patching part, because we might go ahead again

> and log4j was not always included in a cocoon build.

similiar reasons here as for Lucene above

> since both of these situations have changed, can we remove these 
> libraries from lenya?


for the moment I would say yes, but again, we might overtake Cocoon at 
some point again and therefore I think we should keep the patching 
"mechanism" in place

Michi

>
>


-- 
Michael Wechner
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: why do we have our own lucene / log4j jars?

Posted by Antonio Gallardo <ag...@agssa.net>.
On Jue, 20 de Enero de 2005, 0:50, Jean Pierre LeJacq dijo:
> On Wed, 19 Jan 2005, Gregor J. Rothfuss wrote:
>
>> cocoon 2.1.6 has lucene 1.4.3 while we have a 1.4.1 jar in lenya.
>>
>> same for log4j: we have 1.2.8, cocoon 2.1.6 has 1.2.9 in their core
>> libs.
>>
>> if i remember correctly, we have lucene because cocoon used to have 1.3,
>> and log4j was not always included in a cocoon build. since both of these
>> situations have changed, can we remove these libraries from lenya?
>
> +1

++1 ;-)

Best Regards,

Antonio Gallardo



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: why do we have our own lucene / log4j jars?

Posted by Jean Pierre LeJacq <jp...@quoininc.com>.
On Wed, 19 Jan 2005, Gregor J. Rothfuss wrote:

> cocoon 2.1.6 has lucene 1.4.3 while we have a 1.4.1 jar in lenya.
>
> same for log4j: we have 1.2.8, cocoon 2.1.6 has 1.2.9 in their core libs.
>
> if i remember correctly, we have lucene because cocoon used to have 1.3,
> and log4j was not always included in a cocoon build. since both of these
> situations have changed, can we remove these libraries from lenya?

+1

-- 
JP



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org