[forge-issues] [JBoss JIRA] (FORGE-997) bean new-bean not working for all types

Sat Jul 6 08:02:20 EDT 2013

    [ https://issues.jboss.org/browse/FORGE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788005#comment-12788005 ] 

Vineet Reynolds commented on FORGE-997:
---------------------------------------

Thanks for catching this.

I think it would be appropriate to respond with a more suitable error message here (and for other reserved words). Even if a new bean were to be created, the 'import' keyword would be in the incorrect context, thus rendering the class syntactically invalid. The only suitable way of handling this is to validate the user inputs (and the generated code).

> bean new-bean not working for all types
> ---------------------------------------
>
>                 Key: FORGE-997
>                 URL: https://issues.jboss.org/browse/FORGE-997
>             Project: Forge
>          Issue Type: Bug
>    Affects Versions: 1.3.2.Final
>         Environment: Eclipse Kepler + Jboss tools 4
>            Reporter: Hubert Schumacher
>
> forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira