Hi Andrzej,
> > commons-httpclient-3.0-beta1.jar src/plugin/parse-rss/lib > > commons-httpclient-3.0.jar src/plugin/protocol-httpclient/lib > > Not sure what was the reason to use the beta1, perhaps no reason except > that it was the latest available at the moment... Yup, I think that was exactly the reason in the case of parse-rss... > > > > > log4j-1.2.11.jar src/plugin/clustering-carrot2/lib > > log4j-1.2.6.jar 1 src/plugin/parse-rss/lib > > log4j-1.2.9.jar src/plugin/parse-pdf/lib > > > > nekohtml-0.9.2.jar src/plugin/clustering-carrot2/lib > > nekohtml-0.9.4.jar src/plugin/parse-html/lib > > The differences here AFAIK are purely accidental, and I believe we can > just keep the latest releases. Agreed. > > > > > xerces-2_6_2.jar lib > > xercesImpl.jar src/plugin/parse-rss/lib > > Not sure about these ones, but Xerces APIs are pretty stable, so I'd > risk removing xercesImpl.jar . I think that xercesImpl.jar contains classes that are required by parse-rss to function. I haven't investigated in a while, but don't xerces-2_6_2.jar and xercesImpl.jar contain different classes? > > > > > Are there any known reasons to keep multiple versions of things, or > > should we move these each into their own plugin that can be shared? > > The latter is what I advocated for log4j and various xml-related high > level API libs (jdom, dom4j, jaxen). +1 Cheers, Chris > > -- > Best regards, > Andrzej Bialecki <>< > ___. ___ ___ ___ _ _ __________________________________ > [__ || __|__/|__||\/| Information Retrieval, Semantic Web > ___|||__|| \| || | Embedded Unix, System Integration > http://www.sigram.com Contact: info at sigram dot com
