Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "I32 Release Notes"
| (2 intermediate revisions by the same user not shown) | |||
| Line 19: | Line 19: | ||
== Changes to Tigerstripe in Iteration 32: == | == Changes to Tigerstripe in Iteration 32: == | ||
| − | |||
| − | |||
| − | |||
| + | '''Properly handle generator versions specified in model projects (Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=340079 340079])'''<br/> | ||
| + | When OSGi versions were used for Tigerstripe generators and the user specified a version that wasn't available when running generation on a model project, Tigerstripe would throw a null pointer exception. This is now properly handled by displaying an appropriate message to users. | ||
[[Image:generation_version.png]] | [[Image:generation_version.png]] | ||
| Line 31: | Line 30: | ||
'''Generator path specified under preferences is ignored (Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=338956 338956])'''<br/> | '''Generator path specified under preferences is ignored (Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=338956 338956])'''<br/> | ||
The generator path specified under preferences is now properly used when creating new Tigerstripe projects. | The generator path specified under preferences is now properly used when creating new Tigerstripe projects. | ||
| − | |||
[[Image:generation_pref.png]] | [[Image:generation_pref.png]] | ||
| Line 45: | Line 43: | ||
'''Regression with dependency cycle detector (Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=340824 340824])'''<br/> | '''Regression with dependency cycle detector (Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=340824 340824])'''<br/> | ||
| − | There was a regression with an enhancement submitted to detect | + | There was a regression with an enhancement submitted to detect and report back dependency cycles in Tigerstripe projects. In certain cases dependencies were reported to be cyclical when they weren't. This issue is now resolved. |
| Line 54: | Line 52: | ||
'''Defects marked as Invalid:'''<br/> | '''Defects marked as Invalid:'''<br/> | ||
Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=258194 258194] - 0.5 stream committed bugs. | Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=258194 258194] - 0.5 stream committed bugs. | ||
| − | |||
'''Defects marked as 'Works For Me':'''<br/> | '''Defects marked as 'Works For Me':'''<br/> | ||
Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=339540 339540] - [Annotations] In some cases annotation property view is not properly populated when selecting an artifact | Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cgi?id=339540 339540] - [Annotations] In some cases annotation property view is not properly populated when selecting an artifact | ||
Latest revision as of 16:16, 6 April 2011
Summary:
| Major Defects: | 2 |
| Normal Defects: | 7 |
| Total: | 14 |
Changes to Tigerstripe in Iteration 32:
Properly handle generator versions specified in model projects (Bugzilla 340079)
When OSGi versions were used for Tigerstripe generators and the user specified a version that wasn't available when running generation on a model project, Tigerstripe would throw a null pointer exception. This is now properly handled by displaying an appropriate message to users.
Generator path specified under preferences is ignored (Bugzilla 338956)
The generator path specified under preferences is now properly used when creating new Tigerstripe projects.
Stack overflow during a refactoring operation (Bugzilla 337842)
When users refactored artifacts contained in projects that had cyclical dependencies, the operation would result in a Stack Overflow error. Issue is now resolved.
Issues with creating Exception artifacts (Bugzilla 339466)
This was an issue with creating Exception artifacts where it would cause an event loop exception.
Regression with dependency cycle detector (Bugzilla 340824)
There was a regression with an enhancement submitted to detect and report back dependency cycles in Tigerstripe projects. In certain cases dependencies were reported to be cyclical when they weren't. This issue is now resolved.
Couple of issues resolved regarding usage of facets with stereotype-based exclusion (Bugzilla 338992 338917)
First issue was a minor change in behavior and the second issue was an Invalid Thread Access where SWT manipulation was being done on a non-UI thread.
Defects marked as Invalid:
Bugzilla 258194 - 0.5 stream committed bugs.
Defects marked as 'Works For Me':
Bugzilla 339540 - [Annotations] In some cases annotation property view is not properly populated when selecting an artifact