On 12/01/2011, at 11:33 PM, Tamás Cservenák wrote: > In short, it's the Maven3 model (vs Maven2.x model) + Aether (vs > maven-artifact 2.x) + Lucene 3.0.3 (vs Lucene 2.4.1) and MINDEXER-2 that > introduced some important API change.
Sounds reasonable, I was just curious. > > For historical reasons (unfortunately), Indexer API contains Lucene classes, > hence library consumer is simply _forced_ to upgrade. This might cause > trouble if Lucene is used in other places too in same app. If you consider > "plain java" apps (neglect OSGi and related stuff), this change forces the > consuming app to change a _lot_ on it's classpath. Yes, I'm familiar with it ;) I should be able to test it a bit tomorrow. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
