Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0, 1.1.0
-
Fix Version/s: 1.1.1
-
Component/s: Petals Tools
-
Security Level: Public
-
- Environment:
- All.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Issue Type | Improvement [ 4 ] | Bug [ 1 ] |
| Priority | Trivial [ 5 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Trivial [ 5 ] | Minor [ 4 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Summary | The SA builder should test the existence of the referenced SU in the workspace and not on the disk | SA projects should also be built when a SU project is removed / refreshed / created |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 1.1.1 [ 10078 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
In fact, a SA project is validated in two cases:
+ If a file from the project has changed.
+ If a file from one of the SU projects has changed.
It does not handle deletion, refresh and closure actions that could be performed on a SU project.
The SA builder should in fact register a resource listener and listen to all the resource changes.
It would start a full build of the SA project if any change occurs on one of its SU projects.
This mechanism should replace the current one, where it is the SU builder that triggers a full SA validation for the second case.