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 "TigerstripeF2F 20080716"
(→Candidate Topics) |
|||
| Line 5: | Line 5: | ||
== Candidate Topics == | == Candidate Topics == | ||
| − | === | + | === Versioning/distribution of generators on website === |
=== Bugzilla review === | === Bugzilla review === | ||
=== XMI Import/export vs. UML import/export === | === XMI Import/export vs. UML import/export === | ||
| Line 11: | Line 11: | ||
* Annotations definitions link-issues in Tigerstripe generators | * Annotations definitions link-issues in Tigerstripe generators | ||
* '''Annotations in Facets:''' Enhancement to do inclusions and exclusions based on annotations is currently in progress. Functionality has been tested with JUnit, but not included in UI at this point. Facet xml file stores inclusion or exclusion patterns using annotation id (pkg + name of EMF class). An audit will be required. | * '''Annotations in Facets:''' Enhancement to do inclusions and exclusions based on annotations is currently in progress. Functionality has been tested with JUnit, but not included in UI at this point. Facet xml file stores inclusion or exclusion patterns using annotation id (pkg + name of EMF class). An audit will be required. | ||
| − | * '''Abstract Associations:''' Abstract Associations and abstract Associations Classes are not | + | * '''Abstract Associations:''' Abstract Associations and abstract Associations Classes are not being walked through during facet resolution. If a concrete subclass is defined in a facet scope and pulled in the abstract parent was also included. Now that we support generations requiring multiple components we don't necessarily see abstract parent (if contained in other component). This issue has been resolved and the generation will now walk associations between components. |
| − | * '''Facet | + | * '''Facet Meta-Data:''' Dynamic meta-data defined in facets to be accessible from generators (name value pairs). Generator would expect entries from facets and process accordingly (name + group of strings for first implementation). |
=== IPackageArtifact adapters (Bug 240246) === | === IPackageArtifact adapters (Bug 240246) === | ||
=== Package representation in class diagrams (GMF re-gen) === | === Package representation in class diagrams (GMF re-gen) === | ||
Revision as of 13:30, 16 July 2008
Contents
- 1 Candidate Topics
- 1.1 Versioning/distribution of generators on website
- 1.2 Bugzilla review
- 1.3 XMI Import/export vs. UML import/export
- 1.4 Componentized model issues
- 1.5 IPackageArtifact adapters (Bug 240246)
- 1.6 Package representation in class diagrams (GMF re-gen)
- 1.7 Status of UI Testing and inclusion in automated builds
- 1.8 Annotation API on IModelComponents
< To: Tigerstripe Face2Face Meetings
Agenda to be defined. We will work out a schedule on site based on the candidate topics below.
Candidate Topics
Versioning/distribution of generators on website
Bugzilla review
XMI Import/export vs. UML import/export
Componentized model issues
- Annotations definitions link-issues in Tigerstripe generators
- Annotations in Facets: Enhancement to do inclusions and exclusions based on annotations is currently in progress. Functionality has been tested with JUnit, but not included in UI at this point. Facet xml file stores inclusion or exclusion patterns using annotation id (pkg + name of EMF class). An audit will be required.
- Abstract Associations: Abstract Associations and abstract Associations Classes are not being walked through during facet resolution. If a concrete subclass is defined in a facet scope and pulled in the abstract parent was also included. Now that we support generations requiring multiple components we don't necessarily see abstract parent (if contained in other component). This issue has been resolved and the generation will now walk associations between components.
- Facet Meta-Data: Dynamic meta-data defined in facets to be accessible from generators (name value pairs). Generator would expect entries from facets and process accordingly (name + group of strings for first implementation).