Bugzilla – Full Text Bug Listing
| Summary: | No handling for transitive dependencies | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Steve Jerman <sjerman> | ||||
| Component: | Core | Assignee: | Project Inbox <tigerstripe.core-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | chrhartl, nmehrega | ||||
| Version: | 0.5 | ||||||
| Target Milestone: | 0.5M0 | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
If you right click on the 'physical' model in the diagram and select 'go into' you will see that it a depends on party.... we have had multiple cases where this has caused problems with generation. Can you give an example of the generation issues. Headless generation has been modified to throw an exception when transitive dependencies are missing. It will no longer silently fail. *** This bug has been marked as a duplicate of bug 332454 *** |
Created attachment 186197 [details] Screenshot Tigerstripe doesn't deal with transitive dependencies between projects. If project A depends on Project B which depends on project C, project C doesn't automatically get included in Project A's scope. In a 'normal' workspace this doesn't cause issues since all the projects need to be present so that they are all valid. It does raise issues when using modules. For instance, the screen shot only the directly referenced models. .... it all compiles correctly but generation won't necessarily work right since 'physical' references several other modules not just foundation. Tigerstripe should handle the transitive dependencies in this case. Not that the generation failures are all silent.