Consistent profile tagged value names between UML14 and UML2 implementations 
@andromda. vs andromda_
----------------------------------------------------------------------------------------------------

                 Key: MISC-54
                 URL: http://jira.andromda.org/browse/MISC-54
             Project: Miscellaneous
          Issue Type: Improvement
    Affects Versions: 3.4-SNAPSHOT
         Environment: Andromda 3.4-SNAPSHOT
            Reporter: Bob Fields
            Assignee: Bob Fields
            Priority: Minor
             Fix For: 3.4-SNAPSHOT


UML14 profiles use @andromda.whatever naming convention. UML2 profiles use 
andromda_whatever naming convention. @andromda.whatever cannot be migrated to 
EMF UML2 because @ and . are characters that cannot be used in Stereotype 
attribute identifier names in Java (the profile migration process renames 
them). UML14 names should be migrated to the UML2 naming convention, and all 
documentation + references updated. Renamed UML14 taggedValues still retain the 
original xmi:id value, which means no changes required to the referencing UML14 
model. Right now we check for both naming conventions and return true if either 
one matches, allowing for gradual migration of profile values and configuration 
and documentation information.

Also, a number of UML14 test model taggedValues do not belong to any profiles. 
Performing a test migration for each shows which ones are unattached, so those 
test models need to be fixed. UML2 taggedValues (Stereotype attributes) must 
belong to a particular stereotype, can no longer be dynamically added to a 
model element without the stereotype.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 

Reply via email to