use the http connector so that I can completely remove the altrmi code. There are
several parts of the manager project that are designed around the altrmi usage.
Once that is gone, I will be able to consolidate a lot of that code and greatly simplify
it. I have also been working on docs.
I am working on it bit by bit when I get time between regular projects but it is coming
along quite nicely. Give me a week or two and I should have this cleaned up.
I had originally created 3 projects, instrument, instrument-manager, and
instrument-client so that the whole thing could build in the old ant build system
at avalon. Several other projects depended on instrument. But instrument-manager
depends on several of those projects and needs to be built later. Someone else
further broke the instrument-manager project into instrument-http, instrument-altrmi,
instrument-spi and instrument-impl.
Cheers, Leif
Mauro Talevi wrote:
Hi,
looking at the three top-level excalibur instrument projects - instrument, instrument-client, instrument-manager - it seems they could
do with a bit of a consolidation, as follows:
- have a single top-level excalibur instrument project with the subprojects:
- api
- impl
- http
- altrmi
- client
- api would contain what is currently in instrument and instrument-manager/spi projects, under the pacakge
org.apache.excalibur.instrument
I don't really understand the rationale for the spi subproject,
as it the org.apache.excalibur.instrument.manager.interfaces package
contains a mix of interfaces, classes and utils.
Perhaps I'm missing something. Can somebody shed some light?
- the other subprojects would be as the are now, simply moved to a new filestructure that would allow to build the instrument related jars in a single multiproject command.
Also, the maven groupId for these artifacts already reflects this structure - being excalibur-instrument.
As for back-compatibility, my understanding is that 1.2 has not been released yet. Is that correct? Anybody know of current users of 1.2?
On a more general note, I'd like to move towards a version convention that uses -dev postfix for any version in current development and
set exact version only for realeased versions.
Thoughts?
Cheers
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
