[forge-issues] [JBoss JIRA] (FORGE-245) Support structured options in @Commands
Lincoln Baxter III (JIRA)
jira-events at lists.jboss.org
Wed Feb 27 16:59:00 EST 2013
[ https://issues.jboss.org/browse/FORGE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lincoln Baxter III updated FORGE-245:
-------------------------------------
Fix Version/s: 2.0.0.Alpha2
(was: 2.0.0.Alpha1)
> Support structured options in @Commands
> ---------------------------------------
>
> Key: FORGE-245
> URL: https://issues.jboss.org/browse/FORGE-245
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin API
> Reporter: Max Rydahl Andersen
> Fix For: 2.0.0.Alpha2
>
>
> ver considered allowing something like
> generateEntities(@Option String table, @Option String catalog, @Option @Option String schema, @NestedOption final JPADataSource datasource)
> class DataSource {
> public DataSource(@Option(...) String name, @Option(..) password, @Option(..) ..)
> ...
> )
> Which would actually provide some more nested structure and be useful in ui construction in IDE plus better naming of things even in shell ?
> Would also be good to be able to reference "default" @JPADatasource should be "production", "dev" or "test" if SEAMFORGE-210 comes to life?
--
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
More information about the forge-issues
mailing list