[forge-dev] Fwd: [JBoss JIRA] Updated: (SEAMFORGE-211) Support structured options in @Commands

Lincoln Baxter, III lincolnbaxter at gmail.com
Thu Sep 29 10:37:01 EDT 2011


I have a few "JBoss Style" responses that come to mind ;) but I really am
not sure how we can do that without this feature right now. You might do
things like group options by type. Strings with Strings, etc. You probably
would also want to prioritize custom @Option types higher, since those are
usually more relevant to the command at hand.

We really need this feature.
~Lincoln

On Thu, Sep 29, 2011 at 6:39 AM, Max Rydahl Andersen <
max.andersen at redhat.com> wrote:

> Any recommendations on how we avoid just showing a dull long list in the
> IDE when no grouping possible ?
>
> /max
>
> Begin forwarded message:
>
> > From: "Lincoln Baxter III (JIRA)" <jira-events at lists.jboss.org>
> > Subject: [JBoss JIRA] Updated: (SEAMFORGE-211) Support structured options
> in @Commands
> > Date: September 28, 2011 21:04:26 GMT+02:00
> > To: max.andersen at redhat.com
> >
> >
> >     [
> https://issues.jboss.org/browse/SEAMFORGE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >
> > Lincoln Baxter III updated SEAMFORGE-211:
> > -----------------------------------------
> >
> >    Fix Version/s: Future
> >
> >
> >> Support structured options in @Commands
> >> ---------------------------------------
> >>
> >>                Key: SEAMFORGE-211
> >>                URL: https://issues.jboss.org/browse/SEAMFORGE-211
> >>            Project: Seam Forge
> >>         Issue Type: Feature Request
> >>           Reporter: Max Rydahl Andersen
> >>            Fix For: Future
> >>
> >>
> >> 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.
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >
> >
>
> /max
> http://about.me/maxandersen
>
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20110929/8396f45a/attachment.html 


More information about the forge-dev mailing list