Right now you have to define the properties declared in the ant.properties.sample files. That appears to be how all the other required jars are being referenced. How should this be done now? In the all directory, there is the lib directory, but it does not make sense to have copies of the jars in each sub-project which needs them.
Leif Paul Hammant wrote: > Leif, > > Dude, I have checked in some updated altrmi jars to commons. > > Where are the equivlent jars in the excalibur CVS? > > How do I launch a test that illustrates the problem# > > Cheers, > > - Paul > >> Sorry for the long delay. Work has been busy <:-} >> >> I spent some time this weekend and got the basics of the instrument >> package >> working. Things have been divided into 3 sub projects to make the >> interdependencies between sub projects work correctly. >> >> The first is the "instrument" sub project. This project contains all >> of the classes that most classes need to make themselves fully >> instrumentable. >> this package has no dependencies so it is quite flexible. >> >> The second is the "instrument-manager" sub project. This project >> contains >> the InstrumentManager classes which actually collect data and do all >> of the >> profiling. It also contains an InstrumentComponentManager(ICM) >> implementation >> which works the same as the old ProfilerComponentManager. >> This project is not yet 100% complete. I still have to get state >> saving/loading >> working again. And also implement dynamic InstrumentSamples. Soon. >> >> The third is the "instrument-client" sub project. This project >> implements the >> remote client GUI which can be used to connect to one or more remote >> InstrumentManagers. The parts that are implemented are working, but >> it still >> needs some more work. >> Currently, you can connect to multiple remote IMs and view pre configured >> InstrumentSample data. (But it only works for localhost right now.) >> >> To try things out. >> Run the examples in both the instrument-manager and instrument-client >> sub projects. >> Things work much as they did in the altprofile package. >> >> Known problems: >> Currently, altrmi is kicking out some stack traces when the server is >> killed. The >> client will correctly reconnect, but you have to bear with the stack >> traces for >> now. Paul is working on fixing this. :-) >> >> I'll give a more thorough overview once things are nailed down a bit >> more. >> >> Marcus, thanks for all your posts on the altprofile code. I am >> working on getting >> them all integrated. >> >> Cheers, >> Leif >> >> Marcus Crafter wrote: >> >>> Hi Leif! >>> >>> Hope things are going well mate. >>> >>> What's the current status on the profiling/instrumenting code ? >>> How is it all going ? Our discussions finished up a few weeks >>> back with the excalibur rearrangements, what was left to discuss ? >>> >>> (I think we were talking about history managers, and dynamically >>> modifying sample intervals via the gui tool ?). >>> While the rearrangements have been going on I've done some >>> work on >>> the gui tool with jtree's and jtable's, etc. >>> Looking forward to helping out where ever I can. >>> >>> Cheers, >>> >>> Marcus >>> >>> >> >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: >> <mailto:[EMAIL PROTECTED]> >> >> >> > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
