[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7273) IOException: Cannot obtain a location URI for .classpath when deleting project deployed on the server

Rob Stryker (JIRA) jira-events at lists.jboss.org
Wed Mar 16 19:52:47 EDT 2011


     [ https://issues.jboss.org/browse/JBIDE-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-7273.
--------------------------------

    Fix Version/s: 3.3.0.M1
       Resolution: Done


Seems to be in our build now last I checked. 

> IOException: Cannot obtain a location URI for .classpath when deleting project deployed on the server
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-7273
>                 URL: https://issues.jboss.org/browse/JBIDE-7273
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS, UpStream
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Lukas Jungmann
>            Assignee: Rob Stryker
>             Fix For: 3.2.1, 3.3.0.M1
>
>
> -create a new dynamic web project for JBossAS-6.0M5 (runtime shouldn't matter)
> -create some dummy index.jsp file
> -run the project on the server
> -delete the project including its sources
> => ide log says:
> java.io.IOException: Cannot obtain a location URI for L/h/.classpath
> 	at org.eclipse.jdt.internal.core.JavaProject.readFileEntriesWithException(JavaProject.java:2427)
> 	at org.eclipse.jdt.internal.core.JavaProject.readFileEntries(JavaProject.java:2461)
> 	at org.eclipse.jdt.internal.core.JavaProject.readRawClasspath(JavaProject.java:2499)
> 	at org.eclipse.jst.common.jdt.internal.javalite.JavaProjectLite.readRawClasspath(JavaProjectLite.java:116)
> 	at org.eclipse.jst.common.internal.modulecore.AddMappedOutputFoldersParticipant.getMappedJavaOutputContainers(AddMappedOutputFoldersParticipant.java:94)
> 	at org.eclipse.jst.common.internal.modulecore.AddMappedOutputFoldersParticipant.finalize(AddMappedOutputFoldersParticipant.java:74)
> 	at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.runFinalizations(FlatVirtualComponent.java:153)
> 	at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:122)
> 	at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.getChildModules(FlatVirtualComponent.java:111)
> 	at org.eclipse.wst.web.internal.deployables.FlatComponentDeployable.getExportModelChildren(FlatComponentDeployable.java:172)
> 	at org.eclipse.wst.web.internal.deployables.FlatComponentDeployable.getModules(FlatComponentDeployable.java:183)
> 	at org.jboss.ide.eclipse.as.wtp.core.util.ServerModelUtilities.getChildModules(ServerModelUtilities.java:61)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.doGetParentModules(DeployableServer.java:85)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getRootModules(DeployableServer.java:67)
> 	at org.eclipse.wst.server.core.internal.Server.getRootModules(Server.java:2400)
> 	at org.eclipse.wst.server.core.ServerUtil.modifyModules(ServerUtil.java:348)
> 	at org.eclipse.jst.j2ee.refactor.listeners.ProjectRefactoringListener$2.runInWorkspace(ProjectRefactoringListener.java:262)
> 	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list