Community
Participate
Working Groups
Build Identifier: While trying to extend the Component Diagram I found a bug which produces an broken generator model (gmfgen file). The simplest way to produce the bug is as follows: 1. be sure to have the latest componentDiagram.gmfmap file 2. create a new generator model from this mapping file (I had five validation error to ignore) 3. the generation process comes out with nine validation errors in the gmfgen-file (when I validate the original file from the repository I only have six errors) These three additional validation errors are concerning the custom Parsers - The feature 'uses' of 'Custom Parser org.eclipse.uml2.diagram.common.parser.stereotype.ClassifierAppliedStereotypeParser' with 0 values must have at least 1 values - The feature 'uses' of 'Custom Parser org.eclipse.uml2.diagram.common.parser.stereotype.DependencyAppliedStereotypeParser' with 0 values must have at least 1 values - The feature 'uses' of 'Custom Parser org.eclipse.uml2.diagram.common.parser.stereotype.PackageAppliedStereotypeParser' with 0 values must have at least 1 values In the Properties View are no values for 'Label Facets using this parser', which are in the original generator model. I have no clue why this isnformation is gone missing. Reproducible: Always
Created attachment 174288 [details] broken gmfgen for class diagrams I simply tried to create a new generator model from the classDiagram.gmfmap without having made any changes to the gmfmap file previously. I attached the resulted gmfgen. I have all dependencies installed to my target platform which are required for this U2T version: 0.9.0 / I20100708 (2010/07/08)
Created attachment 174479 [details] CompD recreated with I20100708 and 3.6R versions of dependencies
Unfortunately I can't reproduce the problem, attached above please see the results gmfgen files recreated in my environment.
I managed to get it working when I have the gmf-tooling plugins checked out from CVS and imported in my development workspace. But I don't know why this is working now. Maybe this bugzilla could be closed now...
Was only a setup problem of my development workspace.