Generally I was successful using Eclipse to debug server components.
As Paul mentioned for each of the modules different steps are required
to deploy the changes.
I build the jar using maven inside the module directory. With this
approach I have experienced a litte problem. Because Eclipse is
r
Heinz, what you're describing has been my experience with Eclipse as
well. Depending on which part of Geronimo you change there are
different ways to get your changes loaded into the debug env. In some
cases you can rebuild and then redeploy the code using the command
line interface, perhaps fr
On Aug 28, 2006, at 1:17 PM, Heinz Drews wrote:Hi Sachin,The mvn eclipse:eclipse generates the .project files with the proper reference.This solves the problem you mentioned. Generally it would be a nicestart but naturally is the manual import a long and tedious exercise.I guess an exported worksp
Hi Sachin,
The mvn eclipse:eclipse generates the .project files with the proper reference.
This solves the problem you mentioned. Generally it would be a nice
start but naturally is the manual import a long and tedious exercise.
I guess an exported workspace might help.
With debugging there is c
One of the big problems is that you can not use pure Eclipse to develop Geronimo. (just make code changes and compile) The maven eclipse plugin generates the .classpath in which all the projects reference only the built jars in the maven repository rather then the projects set up to reference each
Hello,
I want to use Eclipse for development and debugging of Geronimo components.
The Eclipse plugin I have already used for application development.
I have run mvn eclipse:eclipse, imported manually the projects but I'm
hoping for a faster approach. And I'm facing several problems. First
I co
