[ https://issues.jboss.org/browse/SEAMFORGE-64?page=com.atlassian.jira.plug... ] Lincoln Baxter III closed SEAMFORGE-64. --------------------------------------- Labels: maven (was: ) Assignee: Lincoln Baxter III Fix Version/s: 1.0.0.Alpha3 Resolution: Done Done... [example] example $ [example] example $ project repository- repository-list repository-remove repository-add [example] example $ project repository-list [example] example $ project repository-add CENTRAL JBOSS_NEXUS JBOSS_LEGACY JAVA_NET CUSTOM [example] example $ project repository-add JBOSS_ JBOSS_NEXUS JBOSS_LEGACY [example] example $ project repository-add JBOSS_NEXUS Added repository [JBOSS_NEXUS->http://repository.jboss.org/nexus/content/groups/public] [example] example $ project repository-add CENTRAL Added repository [CENTRAL->http://repo1.maven.org] [example] example $ project repository-list JBOSS_NEXUS->http://repository.jboss.org/nexus/content/groups/public CENTRAL->http://repo1.maven.org [example] example $ > add-repository should offer a built-in list of known repositories > ----------------------------------------------------------------- > > Key: SEAMFORGE-64 > URL: https://issues.jboss.org/browse/SEAMFORGE-64 > Project: Seam Forge > Issue Type: Feature Request > Components: Shell > Affects Versions: 1.0.0.Alpha2 > Reporter: Dan Allen > Assignee: Lincoln Baxter III > Labels: maven > Fix For: 1.0.0.Alpha3 > > > We can anticipate most of the repositories the user is going to want to add (the JBoss Nexus repository being the most likely choice). add-repository should allows the user to select from a built-in list of well-known repositories if they don't provide a URL on the commandline. The list could even be read from the .forge directory, so that the user can globally define repositories from which they want to be able to select. > add-repository <ENTER> > Please select a repository: > [1] CENTRAL - http://repo1.maven.org > [2] JBOSS_NEXUS - http://repository.jboss.org/nexus/content/groups/public > [3] JBOSS_LEGACY - http://repository.jboss.org/maven2 > [3] JAVA_NET - http://download.java.net/maven/2/ > [4] CUSTOM > Selecting CUSTOM would prompt the user for a URL. > The repository name should have a reasonable default, which can be overridden by supplying a name on the commandline. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Enums were cool then and they're still cool now! On Tue, Mar 15, 2011 at 2:50 PM, Max Andersen <manderse(a)redhat.com&gt; wrote: Btw. How Come forge is so eager on using all capital letter for names ? Just look so 80ies :) Sent from a mobile device On 15/03/2011, at 18.52, "Lincoln Baxter III (JIRA)" <jira-events(a)lists.jboss.org&gt; wrote: > > [ https://issues.jboss.org/browse/SEAMFORGE-64?page=com.atlassian.jira.plug... ] > > Lincoln Baxter III closed SEAMFORGE-64. > --------------------------------------- > > Labels: maven (was: ) > Assignee: Lincoln Baxter III > Fix Version/s: 1.0.0.Alpha3 > Resolution: Done > > > Done... > > [example] example $ > [example] example $ project repository- > repository-list repository-remove repository-add > [example] example $ project repository-list > [example] example $ project repository-add > CENTRAL JBOSS_NEXUS JBOSS_LEGACY JAVA_NET CUSTOM > [example] example $ project repository-add JBOSS_ > JBOSS_NEXUS JBOSS_LEGACY > [example] example $ project repository-add JBOSS_NEXUS > Added repository [JBOSS_NEXUS->http://repository.jboss.org/nexus/content/groups/public] > [example] example $ project repository-add CENTRAL > Added repository [CENTRAL->http://repo1.maven.org] > [example] example $ project repository-list > JBOSS_NEXUS->http://repository.jboss.org/nexus/content/groups/public > CENTRAL->http://repo1.maven.org > [example] example $ > > >> add-repository should offer a built-in list of known repositories >> ----------------------------------------------------------------- >> >> Key: SEAMFORGE-64 >> URL: https://issues.jboss.org/browse/SEAMFORGE-64 >> Project: Seam Forge >> Issue Type: Feature Request >> Components: Shell >> Affects Versions: 1.0.0.Alpha2 >> Reporter: Dan Allen >> Assignee: Lincoln Baxter III >> Labels: maven >> Fix For: 1.0.0.Alpha3 >> >> >> We can anticipate most of the repositories the user is going to want to add (the JBoss Nexus repository being the most likely choice). add-repository should allows the user to select from a built-in list of well-known repositories if they don't provide a URL on the commandline. The list could even be read from the .forge directory, so that the user can globally define repositories from which they want to be able to select. >> add-repository <ENTER> >> Please select a repository: >> [1] CENTRAL - http://repo1.maven.org >> [2] JBOSS_NEXUS - http://repository.jboss.org/nexus/content/groups/public >> [3] JBOSS_LEGACY - http://repository.jboss.org/maven2 >> [3] JAVA_NET - http://download.java.net/maven/2/ >> [4] CUSTOM >> Selecting CUSTOM would prompt the user for a URL. >> The repository name should have a reasonable default, which can be overridden by supplying a name on the commandline. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Enums have a to string method one use to make them look less ancient. I actually find the uppercase printout makes them stand out as option values more than they do as plain text

, but also, using the toString() name might make it more difficult to convert back to the object.

Btw. Aren't enums static and thus bad for something like expandable lists ? Most of the lists you're seeing aren't expandable :)

But what in specific are your concerns with this? I may have missed something important.

Well, technically speaking, using toString() sounds like it would make the enums type insensitive. And that would lead to its own problems, no? It sounds like the solution would be to provide lowercased enum constants in this case (should we decide to "step down" the casing ;)

Thoughts? On Wed, Mar 16, 2011 at 7:07 AM, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: On Mar 16, 2011, at 06:20, Lincoln Baxter, III wrote: > > Enums have a to string method one use to make them look less ancient. > > I actually find the uppercase printout makes them stand out as option values more than they do as plain text You do autocomplete - the options are what is there...no matter if its lowercase or uppercase. > , but also, using the toString() name might make it more difficult to convert back to the object. if the tostring is just the lowercased version its not going to be hard ;) > > Btw. Aren't enums static and thus bad for something like expandable lists ? > > Most of the lists you're seeing aren't expandable :) Because they are enums ? :P List of known repositories sounds like something you would like to expand on and not have limited to specific list.... same with many options IMO. > But what in specific are your concerns with this? I may have missed something important. 1) It looks UGLY 2) I have to type capital letters to get the matching options - unless seam forge becomes case insensitive but then you have problems with file matching on most OS's 3) it looks like Seam Forge is SHOUTING at me /max http://about.me/maxandersen -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"