[ 
http://jira.andromda.org/browse/MAVEN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bob Fields updated MAVEN-71:
----------------------------

    Summary: Add maven plugin to run import beautifier in standalone mode 
against an existing code base, fix beautifier import issues  (was: Add aven 
plugin to run import beautifier in standalone mode against an existing code 
base, fix beautifier import issues)

> Add maven plugin to run import beautifier in standalone mode against an 
> existing code base, fix beautifier import issues
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAVEN-71
>                 URL: http://jira.andromda.org/browse/MAVEN-71
>             Project: Maven Plugins
>          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
>
>
> Currently, import beautifier only runs against generated code as a 
> postprocessor step. However, we have also found it useful for existing code 
> cleanup, run in standalone mode against an existing codebase. Beautifier code 
> originally came from org.hybridlabs, now moved to google projects at 
> http://code.google.com/p/hybridlabs-beautifier. Current bugs entered on 
> issues page three months ago but have not even been acknowledged. Maven 
> plugin should also include test data and expected output (same as contained 
> in the google code base). Some current bugs include inner classes not 
> supported, errors with interfaces implementing multiple super interfaces 
> (i.e. with uml.common AssociationClassFacade, before the latest 
> Metafacade.vsl update), and failure to beautify fully qualified class names 
> if the import already exists.
> Also fix the jalopy/antlr parser to not do a stack trace dump when it hits a 
> parse error in a file, just tell me what the mismatch was in a file 
> name:line#.

-- 
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