As the current ApplicationRef validation forbids colon, one more
advantage for using colon as we won't have any backward compatibility
issue in that case? :-)
On 4/27/2010 3:35 PM, Bill Shannon wrote:
> Colon is definitely easier to use, but it's probably also more
> likely to have a conflict with an existing application. From
> a compatibility perspective, how do you plan to handle applications
> with a name that uses whatever delimiter you choose?
>
> Tim Quinn wrote on 04/27/10 08:24 AM:
>> A possible enhancement for GlassFish 3.1 is to support application
>> versioning
>> (http://wiki.glassfish.java.net/Wiki.jsp?page=ApplicationVersioning).
>>
>> The proposal so far has used the semi-colon (';') as the separator
>> between the application name and the version.
>>
>> We are considering changing this to the colon (':') which would give us
>> two advantages:
>>
>> 1. It is much closer to the maven scheme which uses colons as separators
>> in its coordinate strings.
>>
>> 2. Using the semi-colon would require users to enclose the name;version
>> string in single quotes on some OS shells to prevent the shell from
>> interpreting the semi-colon as a separator between two OS commands.
>>
>> Please let us know if you see other advantages or disadvantages of the
>> change.
>>
>> - Tim
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>