- This topic has 5 replies, 3 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version: Windows 2000 SP4
Eclipse version: 3.0.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: Rational ClearCase
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.7.200
Eclipse JDK version: j2sdk1.4.2_03
Application Server JDK version: j2sdk1.4.2_03
Are there any exceptions in the Eclipse log file? yes:*********************************
!ENTRY org.eclipse.ui 4 4 Jul 29, 2004 16:14:00.919
!MESSAGE Unhandled event loop exception!ENTRY org.eclipse.ui 4 0 Jul 29, 2004 16:14:00.919
!MESSAGE Index out of bounds
!STACK 0
java.lang.IllegalArgumentException: Index out of bounds
at org.eclipse.swt.SWT.error(SWT.java:2677)
at org.eclipse.swt.SWT.error(SWT.java:2616)
at org.eclipse.swt.SWT.error(SWT.java:2587)
at org.eclipse.swt.widgets.Widget.error(Widget.java:381)
at org.eclipse.swt.widgets.Combo.getItem(Combo.java:527)
at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizardPage.handleServersComboBoxModified(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizardPage$1.modifyText(Unknown Source)
… <more>
*********************************
– Message Body ——————————-When deploying projects to WebLogic 8.1 SP2, it seems that MyEclipse often fails to update the config.xml file with the proper <Application> element. It generally seems to work when the project is first created on a developer’s machine, then stop working over time. We have noticed the messages shown above in the Eclipse log.
It may also be of note that our project files are shared via ClearCase. We do not share in ClearCase any of the MyEclipse files such as .mymetadata, .myeclipse, .settings. We let MyEclipse create these on each developer’s machine. We do, however, share the .project and .classpath files in ClearCase.
jdimond,
I believe the stacktrace you’re reporting was the signature of a deployment bug in 3.8 Beta 2 that we’ve resolved in the 3.8 GA code stream. However, it may not be related to the issue you’re reporting.
When deploying projects to WebLogic 8.1 SP2, it seems that MyEclipse often fails to update the config.xml file with the proper <Application> element.
First, we don’t make any modifications to config.xml at all. WebLogic does that in response to finding the application in its ‘autoload’ directory.
It may also be of note that our project files are shared via ClearCase. We do not share in ClearCase any of the MyEclipse files such as .mymetadata, .myeclipse, .settings. We let MyEclipse create these on each developer’s machine. We do, however, share the .project and .classpath files in ClearCase.
Is there some reason that the Eclipse JDT’s meta-data files (.project and .classpath) are different than the MyEclipse meta-data file (.mymetadata)? It is in this file that we maintain the interproject relationships, so it’s just as important as the .project and .classpath files for proper functionality. The .myeclipse directory is just for templ files and shouldn’t be in source control. .settings is a new Eclipse 3.0 directory, not one of ours.
Thanks, Scott, for your reply. I didn’t realize that it was WebLogic that was modifying config.xml. That was dumb, I guess. We’ll do more research to see what exactly the problem is. Is there perhaps a WebLogic settings that we can tweak (e.g. refresh interval) that might help us? We will experiment.
As for the .mymetadata file, when we first tried putting .mymetadata in source control along with .project and .classpath, developers would get error messages when importing projects because file was read-only. Also, strange things would happen related to ClearCase – the .mymetadata file would sometimes get marked as writable, but it did not seem to have been properly checked out of ClearCase. With these issues, we just decided not to keep this file in source control, but rather have each developer create a new web project and point to the exisiting Ecilpse project directory in ClearCase.
Incidentally, we also notice that .mymetadata contained the following attribute:
id=”myeclipse.109087…”
This number seemed to be created with a different value on different machines. What is the significance of this value? This was another reason we thought perhaps we should not share the .mymetadata file.
jdimond,
Is it alright to close this issue for now and have you let us know if there is something else that you need help with later?jdimond,
As for the .mymetadata file, when we first tried putting .mymetadata in source control along with .project and .classpath, developers would get error messages when importing projects because file was read-only.
Oh yeah. I forgot that ClearCase and VSS take that read-only view of the world. Maybe your approach is best with those source-control systems.
id=”myeclipse.109087…”
This number seemed to be created with a different value on different machines. What is the significance of this value? This was another reason we thought perhaps we should not share the .mymetadata file.
It’s simply a random but unique number that we can use to identify projects in case you rename them, etc. No real significance except that it won’t change once assigned to a project.
