Skip to main content
aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-08-21Bug 537653 - [EPL] Update java files headersQuentin Le Menez89-180/+360
- replaced the reference in the java files headers - added the SPDX-License-Identifier Change-Id: Ia376515730e2430e8671c2b5c66f7b510894e5c6 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-07-06Bug 533675: [Sequence Diagram] CombinedFragment can be created in anyChristian W. Damus2-4/+249
case in the diagram Test creation of combined fragments - covering nothing at all (in blank space) - partially covering a message - within another combined fragment Also, update the tests for bug 535097 to use the editor fixture to create interaction operands by automation of the creation tool, to better simulate user interaction. This requires explicitly disabling snap to grid (which is on by default in Photon) so that the mouse pointer can be placed as precisely as is required by the tests. Change-Id: Ic68e6c49746d63dc3e7c93ad92bd89ab68937614 Signed-off-by: Christian W. Damus <give.a.damus@gmail.com> Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@cea.fr>
2018-07-06Bug 530201: [Sequence Diagram] Covered feature is broken for InteractionFragmentChristian W. Damus1-1/+7
Ensure that all interaction fragments that can be created in an interaction (continuation apparently not supported) are initialized with lifeline coverage for the lifelines that they visually cover. This includes updating the GridManagementEditPolicy to stop just adding all interaction operands to the 'coveredBys' of all lifelines in the interaction. Change-Id: I6e6dd83138b2433456beacbab1acacb9fb5155a3 Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-07-05Bug 507479: [SequenceDiagram] Choose lifelines covered by a combinedChristian W. Damus2-1/+161
fragment Implement properties view for the InteractionFragment::covered property of combined fragments and interaction operands. Restrict the selection of covered lifelines to lifelines in the same interaction. Add warning constraints for consistency of lifelines covered by - interaction operand as compared to lifelines covered by the fragments that it owns - combined fragment as compared to lifelines covered by fragments of its operands Update the automatic validation (if the preference is set) of an interaction operand that has has its owned fragments recomputed to encompass the entire containing combined fragment, to handle the impact on its lifeline coverage consistency constraint. Update headers & plugin version Change-Id: I340c816a3d62b38b2e811daa90b4d5c0c1fb5493 Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-07-04Bug 535808: [DevTools] Apply Cleanup & Format on saveCamille Letavernier9-18/+231
https://bugs.eclipse.org/bugs/show_bug.cgi?id=535808 - Propagate the new preferences to all projects Change-Id: I0e70c1c4a5d14a24c2d92371c27dad085e9aa2d3 Signed-off-by: Camille Letavernier <cletavernier@eclipsesource.com>
2018-06-12Bug 535794 - [Test] Correct breaking dependency testQuentin Le Menez1-1/+2
- added the missing dependency - modified the missing/incorrect version Change-Id: Ibe05378c453848b99033a7e8216bac8ed890caca Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-06-05Bug 533679: Creation of CFrag should not graphically move elementsChristian W. Damus1-6/+101
Fix the handling of operand ownership for execution specifications to account for (a) that they are not started/finished only by ExecutionOccurrenceSpecifications specifically and (b) that they are not always provided by the rows of the grid model. Since the updating of the rows and columns and fragment ownership is so often done in a read-only context (following operation execution on the history) we can avoid redundant calculations by just always posting the update asynchronously and throttling multiple pending calculations. Altogether this results in the calculation of operand ownership upon initial creation of a combined fragment not being immediately overridden by an incorrect calculation that puts all of the fragments back into the root interaction. https://bugs.eclipse.org/bugs/show_bug.cgi?id=533679 Change-Id: I2abb81a920e2a8a7f20d3a6b702d3194d8e7ae8e Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-06-01Revert "Bug 533804 - [Diagram] Update batik dependencies for 1.9.1"Quentin Le Menez2-11/+1
- This reverts the migration to Batik 1.9.1 as the problems encountered warrant to postpone it This reverts commit aea9db22620bbc8b466b48ea7dd958bd004c91e4. Change-Id: I15546c71d6a1868773a78459e604fe0babefbf6b Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-06-01Bug 528895 - [Quality] Field modifier should follow convention orderBenoit Maggi1-1/+1
- use correct order for field modifier - add missing header - replace C<>line by Celine Change-Id: I2608484da46215dbd65a1e85d47d0aa7706feb58 Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr>
2018-05-29Bug 533676: [Sequence Diagram] Validation should be triggered afterChristian W. Damus2-10/+112
creation of CombinedFragment or InteractionOperand Add custom well-formedness rules to check that messages and execution specifications do not cross interaction operand boundaries. Ensure that re-sizing of an interaction operand triggers validation of that operand and the interaction fragments that it contains, plus any messages originating or terminating within it. Because the default operand of a new combined fragment is now resized upon creation, a new operand is likewise validated for its contents. Fix validation hook and diagnostician extension point schema definitions to match reality of the extension point implementations. Remove UI contributions for validation, to avoid workflow interrution. Validation framework is still slow, but less intrusive for the user. A preference may control the validation activation on user actions. Update the failing compilation on gmfdiag.common.tests. Add a preference to switch on or off the validation. Change-Id: Ic7d83eb18315ce714dc7c71bff38276f330ef260 Also-by: Rémi Schnekenburger <rschnekenburger@eclipsesource.com> Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-05-28Bug 535185 - Add Automatic-Module-Name header for Java 9 compatibilityBenoit Maggi3-0/+3
- add Automatic-Module-Name with the same value as Bundle-SymbolicName in all Manifest.MF - quality fix : remove unused import Change-Id: Icd3e4376bc9e61e360ac61522b967a088a248480 Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr>
2018-05-25Bug 533683: [Sequence Diagram] Deletion of the last InteractionOperandChristian W. Damus1-13/+13
In the diagram, deletion of a multiple selection obtains a deletion command separately from each selected edit-part, entirely within its own context. There is no reasonable way to share a single InteractionContainerDeletionContext amongst these separate requests that will not break other situations, so instead of pre-computing the advice command that deletes the CombinedFragment when it will be left without any operands, this decision is deferred to the actual point of execution of an after advice. https://bugs.eclipse.org/bugs/show_bug.cgi?id=533683 Change-Id: I64b214df5540346c769c1ab769d914b279178e4c
2018-05-14Bug 533699: [Sequence Diagram] InteractionOperand Guard should not be movedChristian W. Damus1-5/+11
Disable moving of interaction operand guards. Resize was already disabled. Add JUnit test coverage for both move and resize. Change-Id: Ibbb29ff64f684b184be1efc6142f7c35df218399 Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-05-14Bug 533672: [Sequence Diagram] InteractionOperand should be created on ↵Christian W. Damus3-21/+195
Lifeline and Interaction Ensure that the Interaction Operand tool is responsive on lifelines where they are covered by combined fragments. Change-Id: Idd29228845e4ac3cd3aa84cbe4d8c4ccd12cf3ce Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-05-14Bug 533671: [Sequence Diagram] CombinedFragment should be created on ↵Christian W. Damus1-9/+7
Lifeline and Interaction Add test coverage for combined fragment creation on lifelines. Change-Id: I9657a74b412fab102422b33e6b85956bdb43f3ae Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-04-25Bug 533682: [Sequence Diagram] Deletion of the InteractionOperand should not ↵Christian W. Damus1-1/+24
delete underlying elements When deleting an interaction operand, instead of deleting contained elements, promote them to the operand or interaction containing the combined fragment. Change-Id: I677807d79ed08c6fac61069aefd37b8c4068238e Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-04-25Bug 533673: [Sequence Diagram] CombinedFragment should be created with one ↵Christian W. Damus4-9/+217
InteractionOperand Add an edit-helper advice to resize the default operand of a new combined fragment to fill the available space in the combined fragment. As this needs to use the edit-part controlling the operand's presentation to obtain a command that resizes the operand and captures the interaction fragments within its bounds, the execution of this advice command is deferred and captured back into the original context for undo/redo. Change-Id: Ifebab84b5b2181bea36d1cd60bf1f9f61adc4fe3 Signed-off-by: Christian W. Damus <give.a.damus@gmail.com>
2018-04-22Bug 533804 - [Diagram] Update batik dependencies for 1.9.1Quentin Le Menez2-1/+11
- Update the targetplatforms to set the required dependency to 1.9.1 from the latest M6 Orbit repository - Rebase the platforms on the latest integration builds Change-Id: Ib57fb5c3b322fcd880ec4f7a7d1ba06b9bfea2a2 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-04-21Revert "Bug 533804 - [Diagram] Update batik dependencies for 1.9.1"Quentin Le Menez1-1/+1
- a compilation error was introduced by this change, this needs to be reverted until resolved. This reverts commit 0bdf62f7a9968d362c762f84a5a3e6da34f9f7a9. Change-Id: Idfb6e8ebd7f04654e22bb017e61d3cd6ea36b65d
2018-04-20Bug 533804 - [Diagram] Update batik dependencies for 1.9.1Quentin Le Menez1-1/+1
- Update tests and dependencies to the new architecture and version - Update the targetplatforms to set the required dependency to 1.9.1 from the latest M6 Orbit repository Change-Id: I07824370934a51062038d382597330833e5ee801 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-03-23Bug 532639: [Table][Matrix] System shall enable to specify the creation ↵Vincent Lorenzo1-1/+1
location of relationships created using a matrix editor. Change-Id: I4ffde565f069e65c85c838bd14aebb4b809c61b7 Signed-off-by: Vincent Lorenzo <vincent.lorenzo@cea.fr>
2018-03-11[Releng] [Photon] Delete old Dev framework and add a new Toolsmiths oneQuentin Le Menez42-3/+3723
- Delete the old Dev releng profile and replace it with a Toolsmith one - Add new features: Junit, Releng, Diagramgen and Debug to be released - Move the junit framework at the root of the junit test folder - Remove Toolsmiths from the main build as it will have its own - Repopulate the SDK feature and distribute the excess features in theit own root parent - Add a new views feature - Moved the assistants to the toolsmiths folder and put them in the toolsmiths build Change-Id: I1c0331b25607baaf1cfcc635d9c7b0d9c6d73e63 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-03-11Bug 531190 - [Releng] Remove generated tests framework and pluginsQuentin Le Menez100-0/+11687
- Remove the generated tests framework - Remove the associated dev plugins and nature to the tests plugins - Remove the xtend files for test generation - Remove the outdated all encompassing test suite - Rewire the dev menu plugin to plain old src instead of src/main/java - Move the junit framework plugins to the root of the junit test folder Change-Id: Id2c0c18762c7c917de93430d3ace2f48940c1297 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>

    Back to the top