[jbosstools-issues] [JBoss JIRA] (JBIDE-16871) use lowercase paths & filenames for JBT & JBDS artifacts

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12956245#comment-12956245 ] 

Nick Boldt commented on JBIDE-16871:
------------------------------------

[~maxandersen], "it seems" is not a valid rationale: pics or it didn't happen. 

As to case sensitivity of Apache (or other http servers), that's been the case forever (unless you're running on a Windows box, and who does that?), but if the user types the URL correctly (or the clicked link is correct) there's no issue.

"Aesthetic" is arbitrary. I prefer "JBossTools" to "jbosstools" even if it's three extra keystrokes to type, because it emphasizes the brand: *JBoss*, not jboss. Which is probably why 5.5 years ago I started publishing update sites using the CamelCaseConvention. Of course that convention was started before me, back in the JBossIDE (2.0.x) days [1] in 2006.

[1] http://download.jboss.org/jbosstools/updates/

So... only real reason above is "consistency".
                
> use lowercase paths & filenames for JBT & JBDS artifacts
> --------------------------------------------------------
>
>                 Key: JBIDE-16871
>                 URL: https://issues.jboss.org/browse/JBIDE-16871
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>    Affects Versions: 4.1.2.Final
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>            Priority: Minor
>             Fix For: 4.2.0.Beta2
>
>
> URLs should avoid any uppercasing if possible, but since our most recent release versions are 7.1.1.GA and 4.1.2.Final (notice the uppercases) that part should stay.
> But rest of our updatesite urls and zips should start aligning to use same naming convention.
> Not "JBossTools-Updatesite" when it should be "jbosstools-updatesite"
> or "jbosstools-Sources.zip" when it should be "jbosstools-sources.zip".

--
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