This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 356603 - Cannot delete Tigerstripe project with JAR file
Summary: Cannot delete Tigerstripe project with JAR file
Status: RESOLVED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 10:31 EDT by Navid Mehregani CLA
Modified: 2011-11-29 05:42 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Mehregani CLA 2011-09-02 10:31:15 EDT
Build Identifier: 

Cannot delete Tigerstripe project with JAR file

Reproducible: Always

Steps to Reproduce:
Try to run 
Create 2 TS projects (One and Two) 
Export TS module as JAR file for project Two 
Add JAR file in project One 
Open tigerstripe.xml file for TS project and add a dependency on a TS module JAR file 
Save changes 
Delete project One 

Project cannot be deleted with JAR file 

Errors running builder 'Cycle References Auditor' on project 'E'. 
org.eclipse.core.internal.resources.ResourceException: Resource '/E/tigerstripe.xml' does not exist. 
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:326) 
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:200) 
at org.eclipse.core.internal.resources.Resource.deleteMarkers(Resource.java:826) 
at org.eclipse.tigerstripe.workbench.internal.builder.CycleReferencesAuditor.cleanMarkers(CycleReferencesAuditor.java:178) 
at org.eclipse.tigerstripe.workbench.internal.builder.CycleReferencesAuditor.validateDescriptor(CycleReferencesAuditor.java:86) 
at org.eclipse.tigerstripe.workbench.internal.builder.CycleReferencesAuditor.validateFirstDescriptor(CycleReferencesAuditor.java:133) 
at org.eclipse.tigerstripe.workbench.internal.builder.CycleReferencesAuditor.incrementalBuild(CycleReferencesAuditor.java:118) 
at org.eclipse.tigerstripe.workbench.internal.builder.CycleReferencesAuditor.build(CycleReferencesAuditor.java:78) 
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629) 
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) 
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172) 
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203) 
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255) 
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) 
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258) 
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311) 
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343) 
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) 
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Anton Salnik CLA 2011-11-29 05:42:59 EST
Issue was fixed.