There have actually been a few incompatible changes to the instrument packages
a couple months ago. They were discussed on the list. It may cause a little little
trouble for container implementations. But the changes will not affect other users
and are good for the long term design of the APIs.
The old packages had a couple design flaws that needed to be cleaned up
before too may users started using the APIs.
The best fix here is to update Phoenix source to work with the new location.
Sorry for the hassle.
Cheers, Leif
Niclas Hedhman wrote:
Leif,
You have at some point made an incompatible change, by moving the NoopInstrumentManager to a different package.
This broke; http://brutus.apache.org/gump/public/avalon-phoenix/avalon-phoenix/gump_work/build_avalon-phoenix_avalon-phoenix.html
which in turn affect another 13 projects.
import org.apache.excalibur.instrument.manager.NoopInstrumentManager;
vs
[EMAIL PROTECTED] instrument]$ jar tf ./api/target/excalibur-instrument-api-1.2-dev.jar | grep Noop.*Manager\.class
org/apache/excalibur/instrument/NoopInstrumentManager.class
I suggest it is put back where it was.
Cheers
Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
