-----Mensagem original----- De: Berin Loritsch [mailto:[EMAIL PROTECTED]
- The debug/classloader is a problem. How do you handle it?
This question is wide open, can you give me some context to focus it a
little?
Yup. How can I debug an application using fortress and still it finding the services.list et all? I though about keeping the components in a jar, and the Main class in eclipse. Stills a burden of regenerate the jar file before each debug.
I'm thinking about how much avalon could complicate the developers day, the pros and cons and so on.
Ah, I see. You are talking about integrating with an IDE or something, corrent? What is necessary to happen is that the ANT task be called to generate the meta info prior to running the application (or at least any time the meta info has changed).
I am working on an application using my GUIApp framework (a fortress based Swing application framework), and I find that I only need to run the ANT task when I have a change in any collected information. As long as the IDE knows where to find all the JARs, it runs quite nicely.
Now, if your application gathers the JARs programatically into a URLClassLoader then you may have to right a "debug" main class that skips this step. That is the only thing I have run into where things may not be as good as it could be.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
