| Summary: | CSpec attributes are empty when bundle is resolved from P2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Jakob Braeuchi <jbraeuchi> | ||||
| Component: | Buckminster | Assignee: | buckminster.core-inbox <buckminster.core-inbox> | ||||
| Status: | REOPENED --- | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | thomas | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Jakob Braeuchi
Created attachment 191678 [details]
Example Plugin
changed to major because restarting eclipse after running a query is very annoying A prebind action is called just prior to when a project is bound to the workspace. That's not the case the second time the query runs. If you don't want to restart your IDE, you can simply remove the project for which the prebind should execute. You don't need to remove the actual files, just the project. As a result, the project will be re-bound to the workspace the next time you run a cquery and that will trigger the prebind action. (In reply to comment #3) > A prebind action is called just prior to when a project is bound to the > workspace. That's not the case the second time the query runs. If you don't > want to restart your IDE, you can simply remove the project for which the > prebind should execute. You don't need to remove the actual files, just the > project. As a result, the project will be re-bound to the workspace the next > time you run a cquery and that will trigger the prebind action. This sounds reasonable. But i do not understand why it works after a restart of the IDE. The project is already in the workspace and the action works as expected. as thomas said, i removed the project with the prebind action and rexecuted the query and the error popped up again. the only thing i can do in this case is restart the workspace. buckminster does not complain about the project with the prebind action itself, the problem comes from a prerequisite that seems to loose it's bundle.jar action when running the query again. |