[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20141:
---------------------------------------------
* I explicitly stated to use composite site, not symbolic links
* I explicitly stated that pointing to core/master is not correct since that is not the updatesite that actually has the structure we expect users to install against (it need be something similar to what is served out by http://download.jboss.org/jbosstools/mars/development/updates/ not core site individually)
* Today http://download.jboss.org/jbosstools/updates/nightly/mars/ point to a site that looks correct - why are you suggesting to point to core sites that will not give the right result when using it as a user ?
Why not do as we do today for http://download.jboss.org/jbosstools/updates/nightly/mars/ ? Which if my memory serves correctly is to point to master composite content and when 4.3.mars start being where nighlty/snapshots are we move the composite (or currently symlink) to point to it ?
> Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20141
> URL: https://issues.jboss.org/browse/JBIDE-20141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build.
> But sometimes, finding these artifacts can be a daunting task.
> Below are some URLs where things can be found.
> *CI builds / SNAPSHOTS / nightlies*
> * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central)
> * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites)
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3....
> ** ..
> * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds)
> *Staging Sites*
> * http://download.jboss.org/jbosstools/mars/staging/builds/
> * http://download.jboss.org/jbosstools/mars/staging/updates/
> *Development Milestones*
> * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*)
> * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance)
> ----
> For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer:
> * https://devstudio.redhat.com/9.0/development/builds/installer/
> Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
- 1
- 0
[JBoss JIRA] (JBIDE-20164) webtools server adapter installation UI is non-informative
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20164:
---------------------------------------------
"JBoss AS, WildFly & EAP server tools" seems like best comprimise if there are no other field we can put info in? no description/comment etc. field available ?
> webtools server adapter installation UI is non-informative
> ----------------------------------------------------------
>
> Key: JBIDE-20164
> URL: https://issues.jboss.org/browse/JBIDE-20164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
> Attachments: Install_New_Extension_and_New_Server.png
>
>
> When using the "download additional adapters" for JBoss Tools it has a few issues.
> a) shows "null" for vendor
> b) does not actually say it is for WildFly nor EAP servers
> c) (idea) should we add OpenShift to this ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
- 1
- 0
[JBoss JIRA] (JBIDE-20164) webtools server adapter installation UI is non-informative
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20164:
----------------------------------------
Summary: webtools server adapter installation UI is non-informative (was: webtools server adapter installation shows "null")
> webtools server adapter installation UI is non-informative
> ----------------------------------------------------------
>
> Key: JBIDE-20164
> URL: https://issues.jboss.org/browse/JBIDE-20164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
> Attachments: Install_New_Extension_and_New_Server.png
>
>
> When using the "download additional adapters" for JBoss Tools it has a few issues.
> a) shows "null" for vendor
> b) does not actually say it is for WildFly nor EAP servers
> c) (idea) should we add OpenShift to this ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
- 1
- 0