| 274 |
<tr> |
<tr> |
| 275 |
<td><font color="#000000">When opening Bugzilla defects, use the Platform/Update |
<td><font color="#000000">When opening Bugzilla defects, use the Platform/Update |
| 276 |
component. Please ALWAYS specify the failing scenario step, and include |
component. Please ALWAYS specify the failing scenario step, and include |
| 277 |
a .zip of the <workspace>/.metadata/ directory</font></td> |
a .zip of the eclipse/.config/ directory</font></td> |
| 278 |
</tr> |
</tr> |
| 279 |
</table> |
</table> |
| 280 |
|
|
| 592 |
in the UI. Go ahead an explore. Remember, is you see something that does |
in the UI. Go ahead an explore. Remember, is you see something that does |
| 593 |
not work, is not correct, or is not what you'd expected, open Bugzilla |
not work, is not correct, or is not what you'd expected, open Bugzilla |
| 594 |
defects in the platform/update component. Please ALWAYS specify the steps |
defects in the platform/update component. Please ALWAYS specify the steps |
| 595 |
leading up to the failure, and include a .zip of the <workspace>/.metadata/ |
leading up to the failure, and include a .zip of the eclipse/.config/ |
| 596 |
directory</font></li> |
directory</font></li> |
| 597 |
</ul> |
</ul> |
| 598 |
|
|
| 621 |
<tr> |
<tr> |
| 622 |
<td><font color="#000000">When opening Bugzilla defects, use the Platform/Update |
<td><font color="#000000">When opening Bugzilla defects, use the Platform/Update |
| 623 |
component. Please ALWAYS specify the failing scenario step, and include |
component. Please ALWAYS specify the failing scenario step, and include |
| 624 |
a .zip of the <workspace>/.metadata/ directory. Note that we ran out of |
a .zip of the eclipse/.config/ directory. Note that we ran out of |
| 625 |
letters, so we are starting from A again. You need to include the part number |
letters, so we are starting from A again. You need to include the part number |
| 626 |
when specifying steps (e.g. 3.A7)</font></td> |
when specifying steps (e.g. 3.A7)</font></td> |
| 627 |
</tr> |
</tr> |
| 667 |
<h2>C. Preserving the state of the optional feature</h2> |
<h2>C. Preserving the state of the optional feature</h2> |
| 668 |
<p>C1. Close Eclipse. Manually delete all 'com.example.*' features from the |
<p>C1. Close Eclipse. Manually delete all 'com.example.*' features from the |
| 669 |
features/ directory and all 'com.example.*' plug-ins from the plugins/ |
features/ directory and all 'com.example.*' plug-ins from the plugins/ |
| 670 |
directory. Delete the '.config' directory in the .metadata directory of the |
directory. Delete the '.config' directory in the eclipse installation directory |
| 671 |
workspace (you want to preserve the bookmark).<br> |
(you want to preserve the bookmark).<br> |
| 672 |
C2. Repeat scenario A but this time leave all the optional features selected.<br> |
C2. Repeat scenario A but this time leave all the optional features selected.<br> |
| 673 |
C3. Restart and open current configuration. Verify that all the features are |
C3. Restart and open current configuration. Verify that all the features are |
| 674 |
showing as enabled.<br> |
showing as enabled.<br> |
| 815 |
I2. After restart, verify that Root 1.0.1 is installed and that all the included |
I2. After restart, verify that Root 1.0.1 is installed and that all the included |
| 816 |
features are version 1.0.1. Also verify that there are no e-fixes left enabled |
features are version 1.0.1. Also verify that there are no e-fixes left enabled |
| 817 |
in the configuration.<br> |
in the configuration.<br> |
| 818 |
I3. Open file ".install-log" in <workspace>/.metadata/.config/ and verify that |
I3. Open file ".install-log" in eclipse/.config/ and verify that |
| 819 |
it contains logs of all the activities performed in scenarios G, H and I.</p> |
it contains logs of all the activities performed in scenarios G, H and I.</p> |
| 820 |
<h2>J. Handling cross-site version conflicts</h2> |
<h2>J. Handling cross-site version conflicts</h2> |
| 821 |
<p>The role of this scenario is to show how cross-site conflicts are handled. |
<p>The role of this scenario is to show how cross-site conflicts are handled. |
Parent Directory
| 
Revision Log
| 
Patch