[jpmdallas0]

Hi,

I am having a small problem.

I have multiple projects in my MyEclipse workspace, and I am using JBoss 3.2.3. When I launch JBoss in debug mode through the IDE (JBoss 3 -> Start) it always uses source files from the first project. How can I tell it which project to use ? I can run JBoss outside of Eclipse and setup my own debugger configuration that specifies the correct project and that will work. But I would prefer to run JBoss from the IDE.

I observed that MyEclipse creates a debugger configuration named jbossServer and I tried setting the project on that configuration but that also didn’t work. It seems MyEclipse generates the configuration dynamically each time the server is started since my changes to that configuration were not persisted.

There appears to be no project setting under the Preferences->MyEclipse->Application Servers, understandably.

Is there some way I can do this short of creating a workspace for each project (which is not desirable) ?

Also I should mention that I am not deploying through MyEclipse. Rather, I am invoking an ant build (through the IDE) that creates an exploded deployment under JBoss.

Thanks,
Joel

[Riyad Kalla]

Jeol,
If the two projects are almost identical in nature you will run into this problem, the trick is to close the project you are not debugging.

[goschino]

Same question for me.

I do not think that having to close other (concurring) projects is a choice of any future: I use to have several instances of the same project according to different CVS branches I work on, which are deployed by an ant script to different WebSphere 5.0 application server instances belonging to one node / cell on the same machine, thus being able to run the servers in parallel and directly compare testing results. In this setting I currently would have to adjust the AppServer settings any time I want to test with another branch, which makes parallel testing complete unfeasable.

The way out would be to attach an AppServer Setup to each (My)Eclipse project, like is now only available centralized in the Prefs dialogue, and take the settings there (just like any other) only as a default for new projects. This way I could even attach 1 ((My)Eclipse) project to >1 different AppServer types. The only ‘generalizing’ issue being not addressed then is having >1 AppServer configurations per AppServer type _and_ project.

Of course it would be nice to have parallel project-driven debugging possibilities on multiple running AppServer instances, improving possibilities to compare issues on different branches of the same project. The question of available resources (as of CPU power and available RAM) should be left to users and not prelimited by design 😉

[Riyad Kalla]

goshino,
You can work around the MyEclipse limitation by using remote debugging (Covered in our documentation section, at the bottom). But the good news longer term is that we will address this in the MyEclipse 5.x series, to allow multiple configs.

[Author]

Posts