I encourage Carsten to wholeheartedly undertake this task. I really
only have two thoughts.
1. I don't think it is a good idea to keep the same package names for
ECM if they are moved into Cocoon. That could be very confusing. I
realize it would be a lot of work to rename existing classes that use
those interfaces, but done on the proper release boundary I think it is
the right thing to do.
2. JMX is the right way to go for instrumentation.
Ralph
- RE: [RT] Building ECM++ for 2.2 Carsten Ziegeler
- Re: [RT] Building ECM++ for 2.2 Ugo Cei
- Re: [RT] Building ECM++ for 2.2 Vadim Gritsenko
- RE: [RT] Building ECM++ for 2.2 Carsten Ziegeler
- Re: [RT] Building ECM++ for 2.2 Ugo Cei
- Re: [RT] Building ECM++ for 2.2 Niclas Hedhman
- Re: [RT] Building ECM++ for 2.2 Bertrand Delacretaz
- Re: [RT] Building ECM++ for 2.2 Niclas Hedhman
- Re: [RT] Building ECM++ for 2.2 Sylvain Wallez
- RE: [RT] Building ECM++ for 2.2 Carsten Ziegeler
- RE: [RT] Building ECM++ for 2.2 Ralph Goers
- RE: [RT] Building ECM++ for 2.2 Carsten Ziegeler
- Re: [RT] Building ECM++ for 2.2 Sylvain Wallez
- Re: [RT] Building ECM++ for 2.2 Daniel Fagerstrom
- RE: [RT] Building ECM++ for 2.2 Ralph Goers
- Re: [RT] Building ECM++ for 2.2 Reinhard Poetz
- Re: [RT] Building ECM++ for 2.2 Sylvain Wallez
- Re: [RT] Building ECM++ for 2.2 Stefano Mazzocchi
- Re: [RT] Building ECM++ for 2.2 Nicola Ken Barozzi
- Re: [RT] Building ECM++ for 2.2 Pier Fumagalli
