<html><body bgcolor="#FFFFFF"><div>Enums have a to string method one use to make them look less ancient. </div><div><br></div><div>Btw. Aren't enums static and thus bad for something like expandable lists ?<br><br>Sent from a mobile device</div><div><br>On 15/03/2011, at 20.23, "Lincoln Baxter, III" <<a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>Enums were cool then and they're still cool now!<br><br><div class="gmail_quote">On Tue, Mar 15, 2011 at 2:50 PM, Max Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com"><a href="mailto:manderse@redhat.com">manderse@redhat.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Btw. How Come forge is so eager on using all capital letter for names ? Just look so 80ies :)<br>
<br>
Sent from a mobile device<br>
<div><div></div><div class="h5"><br>
On 15/03/2011, at 18.52, "Lincoln Baxter III (JIRA)" <<a href="mailto:jira-events@lists.jboss.org"><a href="mailto:jira-events@lists.jboss.org">jira-events@lists.jboss.org</a></a>> wrote:<br>
<br>
><br>
> [ <a href="https://issues.jboss.org/browse/SEAMFORGE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target="_blank"><a href="https://issues.jboss.org/browse/SEAMFORGE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel">https://issues.jboss.org/browse/SEAMFORGE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a></a> ]<br>
><br>
> Lincoln Baxter III closed SEAMFORGE-64.<br>
> ---------------------------------------<br>
><br>
> Labels: maven (was: )<br>
> Assignee: Lincoln Baxter III<br>
> Fix Version/s: 1.0.0.Alpha3<br>
> Resolution: Done<br>
><br>
><br>
> Done...<br>
><br>
> [example] example $<br>
> [example] example $ project repository-<br>
> repository-list repository-remove repository-add<br>
> [example] example $ project repository-list<br>
> [example] example $ project repository-add<br>
> CENTRAL JBOSS_NEXUS JBOSS_LEGACY JAVA_NET CUSTOM<br>
> [example] example $ project repository-add JBOSS_<br>
> JBOSS_NEXUS JBOSS_LEGACY<br>
> [example] example $ project repository-add JBOSS_NEXUS<br>
> Added repository [JBOSS_NEXUS-><a href="http://repository.jboss.org/nexus/content/groups/public" target="_blank"><a href="http://repository.jboss.org/nexus/content/groups/public">http://repository.jboss.org/nexus/content/groups/public</a></a>]<br>
> [example] example $ project repository-add CENTRAL<br>
> Added repository [CENTRAL-><a href="http://repo1.maven.org" target="_blank"><a href="http://repo1.maven.org">http://repo1.maven.org</a></a>]<br>
> [example] example $ project repository-list<br>
> JBOSS_NEXUS-><a href="http://repository.jboss.org/nexus/content/groups/public" target="_blank"><a href="http://repository.jboss.org/nexus/content/groups/public">http://repository.jboss.org/nexus/content/groups/public</a></a><br>
> CENTRAL-><a href="http://repo1.maven.org" target="_blank"><a href="http://repo1.maven.org">http://repo1.maven.org</a></a><br>
> [example] example $<br>
><br>
><br>
>> add-repository should offer a built-in list of known repositories<br>
>> -----------------------------------------------------------------<br>
>><br>
>> Key: SEAMFORGE-64<br>
>> URL: <a href="https://issues.jboss.org/browse/SEAMFORGE-64" target="_blank"><a href="https://issues.jboss.org/browse/SEAMFORGE-64">https://issues.jboss.org/browse/SEAMFORGE-64</a></a><br>
>> Project: Seam Forge<br>
>> Issue Type: Feature Request<br>
>> Components: Shell<br>
>> Affects Versions: 1.0.0.Alpha2<br>
>> Reporter: Dan Allen<br>
>> Assignee: Lincoln Baxter III<br>
>> Labels: maven<br>
>> Fix For: 1.0.0.Alpha3<br>
>><br>
>><br>
>> 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.<br>
>> add-repository <ENTER><br>
>> Please select a repository:<br>
>> [1] CENTRAL - <a href="http://repo1.maven.org" target="_blank"><a href="http://repo1.maven.org">http://repo1.maven.org</a></a><br>
>> [2] JBOSS_NEXUS - <a href="http://repository.jboss.org/nexus/content/groups/public" target="_blank"><a href="http://repository.jboss.org/nexus/content/groups/public">http://repository.jboss.org/nexus/content/groups/public</a></a><br>
>> [3] JBOSS_LEGACY - <a href="http://repository.jboss.org/maven2" target="_blank"><a href="http://repository.jboss.org/maven2">http://repository.jboss.org/maven2</a></a><br>
>> [3] JAVA_NET - <a href="http://download.java.net/maven/2/" target="_blank"><a href="http://download.java.net/maven/2/">http://download.java.net/maven/2/</a></a><br>
>> [4] CUSTOM<br>
>> Selecting CUSTOM would prompt the user for a URL.<br>
>> The repository name should have a reasonable default, which can be overridden by supplying a name on the commandline.<br>
><br>
> --<br>
> This message is automatically generated by JIRA.<br>
> For more information on JIRA, see: <a href="http://www.atlassian.com/software/jira" target="_blank"><a href="http://www.atlassian.com/software/jira">http://www.atlassian.com/software/jira</a></a><br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org"><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a></a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank"><a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a></a><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org"><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a></a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank"><a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a></a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com"><a href="http://ocpsoft.com">http://ocpsoft.com</a></a><br><a href="http://scrumshark.com"><a href="http://scrumshark.com">http://scrumshark.com</a></a><br>"Keep it Simple"<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>forge-dev mailing list</span><br><span><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a></span><br></div></blockquote></body></html>