Skip to main content
aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2020-08-17[Releng] Update launchers and publishing to newer Tycho and platform.Ed Merks1-1/+1
2020-08-17[Releng] Parameterize the Java version to be able to build older TPs.Ed Merks2-3/+26
2020-08-17[Releng] Change pom for doc build to use Java 11.Ed Merks1-1/+1
2020-08-17[Releng] Increment versions for test.xmlEd Merks1-1/+1
Also fix the environment used to run ant. And fix the local tycho build to use Java 11. Signed-off-by: Ed Merks <ed.merks@gmail.com>
2020-06-29[563042] Migrating to the new Xtext generator workflow.Tamas Miklossy34-123/+125
-------------- I. org.eclipse.emf.ecore.xcore plugin ------------------ 1. Modify the GenerateXcore.mwe2 workflow to use the new Xtext generator workflow (org.eclipse.xtext.xtext.generator.*) packages instead of the old deprecated generator workflow (org.eclipse.xtext.generator.*) packages. 2. Rename XcoreJavaValidator to XcoreValidator. 3. Update generated code in the src-gen folder. -------------- II. org.eclipse.emf.ecore.xcore.ui plugin -------------- 1. Move the content assist infrastructure from the org.eclipse.emf.ecore.xcore.ui package into the org.eclipse.emf.ecore.xcore.ide package. 2. Rename XcoreEditor to CustomXcoreEditor to avoid naming collision with the generated editor. Modify the hand-written CustomXcoreEditor to inherit from the generated XcoreEditor. 3. Update plugin.xml_gen 4. Merge plugin.xml_gen into plugin.xml. -------------- III. org.eclipse.emf.test.ecore.xcore plugin ----------- 1. Move the XcoreInjectorProvider from the org.eclipse.emf.ecore.xcore package to the org.eclipse.emf.ecore.xcore.tests package. 2. Add generated XcoreUiInjectorProvider class. 3. Update META-INF/MANIFEST.MF file. -------------- IV. Versions and Builds -------------------------------- 1. Modify the lower bounds of plugin dependencies because minimally Xtext 2.18 is required 2. Ensure that all plugin dependencies have version ranges. 2. Modify the releng POMs so that the build of Xcore and the site, which depends on Xcore, is disabled for target platforms < 2019-06. Change-Id: I81e446995025832dc2e84decc818cfe533293ff4 Signed-off-by: Tamas Miklossy <miklossy@itemis.de>
2020-03-24[releng] Specify phase for tycho-source-feature-plugin.Ed Merks1-0/+1
2020-03-24[releng] Specify tycho version for tycho-source-feature-plugin.Ed Merks1-0/+1
2020-03-22[releng] Update tycho and jarsigner versionsEd Merks1-3/+3
Also use latest p2 to compose repositories.
2020-03-19[releng] Update setup and TP for EMF 2.22 for 2020-06Ed Merks4-2/+51
2020-01-27[releng] Increment versions.Ed Merks1-1/+1
2019-12-20[releng] Create target platform for 2020-03 builds.Ed Merks6-4/+52
2019-12-20[releng] Update target platform for 4.14 release repository.Ed Merks1-1/+1
2019-12-04[releng] Prepare for 2.20 release.Ed Merks1-1/+1
Fix issues for building against 2019-09 target platforms.
2019-12-03[releng] Prepare for 2.20 release.Ed Merks11-2/+14
Fix issues related to building against the Xtext 2.20 release, i.e., make sure the Xcore tests run. Fix issues for building against older target platforms.
2019-12-03[releng] Prepare for 2.20 release.Ed Merks1-3/+3
2019-09-18[releng] Update TP for 2019-12Ed Merks1-1/+1
2019-09-12[releng] Prepare for 2019-12 builds; it doesn't work yet thoughEd Merks2-0/+45
2019-06-25[releng] Reset version baseline for 2.19Ed Merks1-1/+1
2019-06-24[releng] Update target platforms for 2019-09Ed Merks3-1/+46
2019-03-21[releng] Update targets for 2.18 builds against 2019-06Ed Merks4-4/+49
2018-12-20[releng] Use reflection to do manifest merging to remain compatibleEd Merks9-9/+9
Ensure that older platforms such as Helios still build.
2018-12-20[releng] Fix typo in 2019-03.target to use 4.11 I buildEd Merks1-1/+1
2018-12-20[releng] Fix typo in 2019-03.osgi2.targetEd Merks1-0/+0
2018-12-20[releng] Updates for finishing 2018-12 and starting 2019-03Ed Merks16-15/+60
2018-10-26[releng] Updates to support builds for 2018-12Ed Merks3-13/+3
2018-10-18[540287] Updated Eclipse Updates URLKarsten Thoms1-1/+1
4.9-I-builds -> 4.9 Change-Id: I5420c4b45d6822bb2f4850117af7d7613f67f7da Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
2018-09-14[releng] Prepare for 2018-12 target platform and use Xtext 2.15Ed Merks13-12/+57
2018-07-22[releng] Support a 2018-09 target platformEd Merks3-1/+46
2018-06-26[releng] Migrate to EPL 2.0.Ed Merks1-1/+1
2018-06-26[releng] Update target platforms to use the latest Xtext release and forEd Merks9-19/+10
photon to use the photon release repository Also change EMF.setup to use the latest Xtext release.
2018-02-07[438123] Provide for extensible cell editor supportEd Merks9-0/+36
GenDataType and GenFeature both support propertyEditorFactory. These properties are implemented to read directly from GenModel annotations, in which case they don't serialize into the *.genmodel. The GenFeature.propertyEditorFactory, when not specifically set or present as an annotation, derives its value from the value of this property on the GenDataType. Validation is supported. The value must correspond to a registered IPropertyEditorFactory. An IPropertyEditorFactory supports creating cell editors, but it's a generic API. The two primary IItemPropertyDescriptor implementation classes implement IPropertyEditorFactory.Provider and have new constructors for the additional argument; the templates generate the right call when the property is present. The provider can return a URI for a registered factory (there is of course a new extension point to register them) or can return a factory instance. PropertyDescriptor tests for this interface and delegates to the item property descriptor to get the factory; if one is provided, the factory is used. If that actually creates a cell editor, that is of course used. Otherwise the default behavior kicks in to create the cell editor. IPropertyEditorFactory also support specializing the labels used for the values, and supports validation that the URI is well formed. Factory lookup is done by trimming the query, fragment, and successive segments of the URI, so the URI can be used to pass additional arguments to the factory. Reflective item providers look up the annotations so they also support specialized property editors. IPropertyEditorFactory cannot be implemented directly. One of the provided classes must be extended. The implementation classes support suggesting choices of URI values appropriate for the context, or even being omitted because the context doesn't support that type of cell editor. To test out these concepts and the design, a DateConversionDelegate is implemented. It goes the whole nine yards to support annotation validation and specialized property descriptors to suggest formatting choices. It basically supports specialized serialization conversion for long, Long, Date, java.sql.Date, Calendar, GregorianCalendar, and XMLGregorianCalendar. With properly serialized Date types available, NebulaDatePropertyEditorFactory is implemented to demonstrate the concepts. It supports using a Nebula CDateTime cell editor on features or data types with an instance type convertible to a Date, i.e., the ones listed previously as also supported by the date conversion delegate. This implementation used reflection to avoid a hard dependency on Nebula; it's an optional greedy dependency. The implementation illustrates how the propertyEditorFactory URI can be used to specialize the cell editor that's produced and a IPropertyEditorFactory can be used to specialize labels, i.e, although the type in the model might be long, the label that's shown for it can display a date, formatted in any way you like. While working on the validation it became clear that many things being validated rely on what's in the target platform but instead are validating against what's registered the running IDE. CommonPlugin now provides basic support for reading information from the target platform and provides a base registry implementation that can easily be extended to make use of this. EcorePlugin is changed to reuse this new basic implementation to avoid having it's own large PDEHelper class. All this is of course done reflectively so no PDE need be installed, in which case, the behavior is to return what's in the running IDE. Several problems in the auto resizing of columns and the auto expansion of property in the properties view are fixed. EFactoryImpl is changed to use a registered conversion delegate first before trying other approaches. This makes it more efficient to use conversion delegates and is more in keeping with the intent that such a declaration always specialize the behavior of conversion.
2018-01-26[Releng] Reduce the use of large composites for target platformsEd Merks9-27/+144
This includes simplifying the Targlets in EMF.setup and all the *.target files helios through photon.
2018-01-26[Releng] Factor out ed.ui tests specifically for Platform and RAPEd Merks1-0/+2
Leave emf.edit.test as purely an emf.edit test not a emf.edit.ui test. Fix working sets in EMF.setup. Ensure that EMF.setup populates launch favorites.
2018-01-24[Releng] Improve EMF.setup and make Build launches more portableEd Merks1-1/+1
2018-01-23[Releng] Improve EMF.setup and make Build launches portableEd Merks1-2/+2
2018-01-23[529487] Migrate EMF/XSD build to TychoEd Merks25-0/+1069

    Back to the top