- This topic has 9 replies, 3 voices, and was last updated 20 years ago by
.
-
Posts
-
If an EJB project depends on project “A”, during the deployment the code, the code from project “A” gets deployed with the EJB. But if the code in project “A” changes it does not get auotmatically deployed to the exploded EJB project.
Can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.
What operating system and version are you running? Windows 2000
What Eclipse version and build id are you using? (Help > About Eclipse Platform) 3.0.1 200409161125
– Was Eclipse freshly installed for MyEclipse? yes
– If not, was it upgraded to its current version using the update manager?
– Are any other external plugins installed? no
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.* – 8
What MyEclipse version are you using? (Help > About Eclipse Platform > Features) 3.83
What JDK version are you using to run Eclipse? (java -version) 1.4.2_03
What JDK version are you using to launch your application server? 1.4.2_03
What steps did you take that resulted in the issue?
What application server are you using? JBoss 3.2.5
Are there any exceptions in the Eclipse log file? (<workspace>/.metadata/.log) noThanks for bringing this to our attention. I verified what you’re reporting. Class changes for dependent projects are currently sync’d to the remote JVM, so they behave properly while debugging, but the actual class files are not copied to every exploded deployment of every project which uses the project as a dependent project. Minimally, the project deployment should be marked as out of date, and it is not, thus causing confusion. We’ve entered this as a bug and will address it in the next release. In the meantime, the workaround will be to redeploy the EJB project after shutting down the server if you made changes to its dependent projects.
Well, I know it’s a bit inconvenient, but hot debugging will still work fine, since class changes will be hotswapped into the remote JVM as they’re saved in the workspace. This bug simply means that after you get everything working, you’ll need to redeploy the application so that your changes are physically copied to the deployment location so your changes in dependent projects can survive a server restart.
