[icbpi]

Hi guys!

When trying to build one of my web applications, I get the following error:
‘Could not resolve location. The variable named “workspace” does not exist.”

Since this is on build, I’m assuming it’s the Ant “workspace” variable that can’t be found (This is the only “workspace” variable referenced anywhere during build, within the XDoclet Builder.launch file). I have not changed anything relating to the workspace variable; I’m using pretty much a fresh install of MyEclipse. Would you guys happen to know why I’m receiving this error? Here is my info:

OS: Windows 2000, 5.00.2195 Service Pack 3
Eclipse Version: 3.0.0
Build ID: 200308281813
– Eclipse was freshly installed for MyEclipse
Other Plugins: Checkstyle
– There are 8 plugin directories like org.eclipse.pde.*
MyElipse Version: 3.6.2
JDK Version: 1.4.1
Application Server JDK: 1.4.1
Application Server: JBoss 3
Steps taken to create problem:

– Selected my web project in the “MyEclipse” perspective
– Selected “Project -> Rebuild Project” from the menu
– Project starts to build, then get a “Build Problems” error window, with the message “Problems occurred building the selected resources. Could not resolve location. The variable named “workspace” does not exist.

Here is the error from Eclipse’s .log file:

!ENTRY org.eclipse.core.resources 4 2 Sep 19, 2003 10:23:18.423
!MESSAGE Problems occurred when invoking code from plug-in: “org.eclipse.core.resources”.
!STACK 1
org.eclipse.core.runtime.CoreException: Could not resolve location.
at org.eclipse.ui.externaltools.internal.launchConfigurations.ExternalToolsUtil.getLocation(ExternalToolsUtil.java:98)
at org.eclipse.ant.ui.internal.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:83)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:156)
at org.eclipse.ui.externaltools.internal.model.ExternalToolBuilder.launchBuild(ExternalToolBuilder.java:131)
at org.eclipse.ui.externaltools.internal.model.ExternalToolBuilder.build(ExternalToolBuilder.java:69)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:440)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1016)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:128)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:184)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:194)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:154)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1016)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:278)
at org.eclipse.core.internal.resources.Project.build(Project.java:85)
at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:156)
at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:122)
at org.eclipse.ui.actions.WorkspaceAction$1.execute(WorkspaceAction.java:279)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1571)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1588)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
!ENTRY org.eclipse.ui.externaltools 4 0 Sep 19, 2003 10:23:18.423
!MESSAGE Could not resolve location.
!SUBENTRY 1 org.eclipse.debug.core 4 120 Sep 19, 2003 10:23:18.423
!MESSAGE The variable named “workspace” does not exist.
!SUBENTRY 1 org.eclipse.debug.core 4 120 Sep 19, 2003 10:23:18.423
!MESSAGE The variable named “workspace” does not exist.

Thanks very much for your assistance!

octalpus.

[Scott Anderson]

Octalpus,

First, thanks for posting such an extensive amount of information. It makes running this down a bit easier.

I find a couple of things odd about this issue. First, the stacktrace doesn’t go through any of MyEclipse’s code. It’s all 100% Eclipse. Second, I checked one of my XDoclet-based web projects and there is no ‘workspace’ variable defined in any of the files there at all. I’m really stumped trying to tie this to MyEclipse, to tell you the truth. Did you find somewhere that a ‘workspace’ variable is referenced? I found ‘workspace_loc’, but no workspace. Do you have any ideas where ‘workspace’ is referenced? Hmmm….

–Scott
MyEclipse Support

[Stephen Coy]

I am seeing this as well.
The “Xdoclet Builder” that is presumably generated by MyEclipse contains this reference – which keeps being regenerated as:

${workspace:/myApp/xdoclet-build.xml}

I am forever changing it back to “workspace_loc”.

Steve Coy

[Scott Anderson]

Steve,

That’s very interesting and looks like a bug. Can you tell me which doclets and options you’re using so that we can try to replicate it? I’ve got test projects using both the Standard EJB and Standard Web doclets and the generated files are always correct. If we can isolate this, we can address it in the next service release. Thanks in advance for any help you can provide.

By the way, are you also using Eclipse 3.0M3? It appears that this problem is related to the 3.0 builds only at this point.

–Scott
MyEclipse Support

[Scott Anderson]

I dug deeper on this one and identified it as a bug caused by a change the Eclipse team made to IExternalToolConstants between the 3.0M2 and M3 builds that we missed picking up on the last pass through the codebase. It does not effect the MyEclipse 2.6.x products, but will be addressed in the next service release of the 3.6.x product. The workaround until that time is to do what Steve does and change ‘workspace’ to ‘workspace_loc’ in the XDoclet Builder.launch file. Sorry for the inconvenience.

Thanks to all for helping us isolate the problem so we can resolve it.

–Scott
MyEclipse Support

[Stephen Coy]

FWIW, I think it must have been before M2, because it was doing the same thing.

Steve Coy

[icbpi]

Thanks very much for the quick response on this issue! Much appreciated!

octalpus.

[Scott Anderson]

No problem. Thanks for helping us run it down and your patience until we issue a fix.

–Scott
MyEclipse Support

[Author]

Posts