[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=12969587#comment-12969587 ] 

Nick Boldt edited comment on JBIDE-16871 at 5/22/14 2:06 AM:
-------------------------------------------------------------

I assume you mean in CSP & GoldenGate, [~cobrien_redhat], will *rename the files* from jboss-devstudio-8.0.0.Beta2<qualifier>-installer.jar (not zip) to jboss-devstudio-8.0.0.Beta2-installer.jar. 

Also assume similar for the EAP bundle, which I will assume you want to call "installer-eap" rather than "installer". I would also reverse the order of "updatesite" and its qualifier, following the same declining hierarchy model we're using for <provider>, <project>, <asset>. Thus:

{quote}
jboss-devstudio-8.0.0.Beta2<qualifier>-*installer.jar*
jboss-devstudio-8.0.0.Beta2<qualifier>-installer-src.zip
jboss-devstudio-8.0.0.Beta2<qualifier>-*installer-eap*.*jar*
jboss-devstudio-8.0.0.Beta2<qualifier>-updatesite-core.zip
jboss-devstudio-8.0.0.Beta2<qualifier>-updatesite-central.zip
jboss-devstudio-8.0.0.Beta2<qualifier>-updatesite-earlyaccess.zip - new, see JBIDE-17318
{quote}

But when we build them, they will retain their <qualifier> suffixes so dev, releng, QE & GSS can more easily determine what's what. 

I would frankly rather have the <qualifier> appear in CSP & GG too, so that end users can communicate to GSS which exact version they have, rather than just "uh... the 8.0.0.Beta2 build". Also removes a manual processing step for Chris, and avoids any confusion if we ever have to respin/replace a build.

But if [~mmusaji] & Chris O are OK with this simplification when the final bits appear in CSP/GG, then so am I.

Aside: [~maxandersen] if you don't like "installer" and "installer-eap" perhaps "installer-standalone" and "installer-bundle" are better?


was (Author: nickboldt):
I assume you mean in CSP & GoldenGate, [~cobrien_redhat], will *rename the files* from jboss-devstudio-8.0.0.Beta2<qualifier>-installer.*jar* (not zip) to jboss-devstudio-8.0.0.Beta2-installer.*jar*. Also assume similar for the EAP bundle, which I will assume you want to call "installer-eap" rather than "installer". I would also reverse the order of "updatesite" and its qualifier, following the same declining hierarchy model we're using for <provider>-<project>-<asset>. Thus:

{quote}
jboss-devstudio-8.0.0.Beta2<qualifier>-*installer.jar*
jboss-devstudio-8.0.0.Beta2<qualifier>-installer-src.zip
jboss-devstudio-8.0.0.Beta2<qualifier>-*installer-eap*.*jar*
jboss-devstudio-8.0.0.Beta2<qualifier>-updatesite-core.zip
jboss-devstudio-8.0.0.Beta2<qualifier>-updatesite-central.zip
jboss-devstudio-8.0.0.Beta2<qualifier>-updatesite-earlyaccess.zip - new, see JBIDE-17318
{quote}

But when we build them, they will retain their <qualifier> suffixes so dev, releng, QE & GSS can more easily determine what's what. 

I would frankly rather have the <qualifier> appear in CSP & GG too, so that end users can communicate to GSS which exact version they have, rather than just "uh... the 8.0.0.Beta2 build". Also removes a manual processing step for Chris, and avoids any confusion if we ever have to respin/replace a build.

But if [~mmusaji] & Chris O are OK with this simplification when the final bits appear in CSP/GG, then so am I.

Aside: [~maxandersen] if you don't like "installer" and "installer-eap" perhaps "installer-standalone" and "installer-bundle" are better?

> 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
>          Components: build
>    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 was sent by Atlassian JIRA
(v6.2.3#6260)