[JBoss JIRA] (JBIDE-20095) openshift template does not warn/errror on required values
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20095:
---------------------------------------------
why can't we:
a) introduce a convention in putting some labels in descrption to avoid this big 3.0 shortcoming ?
b) knowing 3.0 is very limited here we can still make it possible to undo/delete the things that was created. It should not require several tens of clicks and mouse movements to undo something that was just created by mistake.
> openshift template does not warn/errror on required values
> ----------------------------------------------------------
>
> Key: JBIDE-20095
> URL: https://issues.jboss.org/browse/JBIDE-20095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Jeff Cantrill
> Fix For: 4.3.x
>
>
> using https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v1beta3) a lot of variables are shown, click next/next and all is created except build configs stating "values are required"
> 1) why am I not warned *Before* starting to create things ?
> 2) why cannot undo/delete the things that was created but now useless since buildconfig not created ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20156) Connection wizard: can't create new v3 application when launching wizard from Central
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20156 at 6/29/15 8:22 AM:
-------------------------------------------------------------------
[~deshuai] ok thanks for updating. This is duplicate to JBIDE-19759 and JBIDE-20058
You actually could connect, the error in the wizard tells you that there is no v3 application wizard as described in the following screenshof from JBIDE-19759:
!https://issues.jboss.org/secure/attachment/12389641/12389641_no-application-wizard.png!
was (Author: adietish):
[~deshuai] ok thanks for updating. This is duplicate to JBIDE-19759 and JBIDE-20058
You actually could connect, the error in the wizard tells you that there is no v3 application wizard as described here:
!https://issues.jboss.org/secure/attachment/12389641/12389641_no-application-wizard.png!
> Connection wizard: can't create new v3 application when launching wizard from Central
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-20156
> URL: https://issues.jboss.org/browse/JBIDE-20156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Ma Deshuai
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: login.png
>
>
> OpenShift plug version:
> 3.0.0.Beta2-v20150623-1035-B854
> Steps:
> 1. Open the login dialog from "JBoss Central" -> "OpenShift Application"
> 2. In the login dialog, set server type to "OpenShift v3", set the protocol to "Basic"
> 3. Input userName and Password.
> 4. Click "Next" button
> Expect result:
> Step4 : The "Next" button should enabled.
> Actual result:
> Step4 : The "Next" button is always disabled. so I can't connect to v3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20156) Connection wizard: can't create new v3 application when launching wizard from Central
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20156:
------------------------------------------
[~deshuai] ok thanks for updating. This is duplicate to JBIDE-19759 and JBIDE-20058
You actually could connect, the error in the wizard tells you that there is no v3 application wizard as described here:
!https://issues.jboss.org/secure/attachment/12389641/12389641_no-application-wizard.png!
> Connection wizard: can't create new v3 application when launching wizard from Central
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-20156
> URL: https://issues.jboss.org/browse/JBIDE-20156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Ma Deshuai
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: login.png
>
>
> OpenShift plug version:
> 3.0.0.Beta2-v20150623-1035-B854
> Steps:
> 1. Open the login dialog from "JBoss Central" -> "OpenShift Application"
> 2. In the login dialog, set server type to "OpenShift v3", set the protocol to "Basic"
> 3. Input userName and Password.
> 4. Click "Next" button
> Expect result:
> Step4 : The "Next" button should enabled.
> Actual result:
> Step4 : The "Next" button is always disabled. so I can't connect to v3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20156) Connection wizard: can't create new v3 application when launching wizard from Central
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20156:
-------------------------------------
Summary: Connection wizard: can't create new v3 application when launching wizard from Central (was: Connection wizard: can't connect to openshift v3 via new applicaion dialog)
> Connection wizard: can't create new v3 application when launching wizard from Central
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-20156
> URL: https://issues.jboss.org/browse/JBIDE-20156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Ma Deshuai
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: login.png
>
>
> OpenShift plug version:
> 3.0.0.Beta2-v20150623-1035-B854
> Steps:
> 1. Open the login dialog from "JBoss Central" -> "OpenShift Application"
> 2. In the login dialog, set server type to "OpenShift v3", set the protocol to "Basic"
> 3. Input userName and Password.
> 4. Click "Next" button
> Expect result:
> Step4 : The "Next" button should enabled.
> Actual result:
> Step4 : The "Next" button is always disabled. so I can't connect to v3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20162) Rename FeedHenry references to RHMAP
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20162?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20162:
----------------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-20162 (was: JBDS-3475)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Affects Version/s: (was: 9.0.0.Beta1)
Component/s: aerogear-hybrid
(was: aerogear-hybrid)
Docs QE Status: (was: NEW)
Target Release: (was: 9.0.0.GA)
> Rename FeedHenry references to RHMAP
> ------------------------------------
>
> Key: JBIDE-20162
> URL: https://issues.jboss.org/browse/JBIDE-20162
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
>
> Feedhenry is now called Red Hat Mobile Application Platform adjust branding accordingly
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18578) Additional javaee7-samples import issues
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18578?page=com.atlassian.jira.plugi... ]
Rastislav Wagner reassigned JBIDE-18578:
----------------------------------------
Assignee: Fred Bricon (was: Rastislav Wagner)
> Additional javaee7-samples import issues
> ----------------------------------------
>
> Key: JBIDE-18578
> URL: https://issues.jboss.org/browse/JBIDE-18578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR2
> Environment: JBDS 8.0.0.CR2
> Reporter: Jiri Peterka
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta2
>
>
> Additional javaee7-samples import issues
> Clone and import https://github.com/javaee-samples/javaee7-samples as maven projects
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
> There are still some Java Problems, Maven Problems and XML Problems after import, most projects are without errors. Project should be imported without errors
> Java Problems
> {code}
> Description Resource Path Location Type
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 76 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 85 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 35 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 32 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 36 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
> SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
> SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
> The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" Greeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
> The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" SimpleGreeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
> The declared package "org.javaee7.cdi.nobeans.xml" does not match the expected package "test.java.org.javaee7.cdi.nobeans.xml" GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 1 Java Problem
> The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 3 Java Problem
> The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 4 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 12 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 13 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 14 Java Problem
> {code}
> Maven Problems:
> {code}
> Description Resource Path Location Type
> Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen (execution: default, phase: process-classes) pom.xml /jaxws-endpoint line 21 Maven Project Build Lifecycle Mapping Problem
> Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsimport (execution: default, phase: generate-sources) pom.xml /jaxws-client line 21 Maven Project Build Lifecycle Mapping Problem
> {code}
> and xml problems
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.1: Element 'jboss' must have no character or element information item [children], because the type's content type is empty. enforce-beans.xml /jax-rs-angularjs/src/test/resources line 4 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 25 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 25 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 28 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jaxrs-endpoint/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-embedded line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-remote line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-jbosseap-remote line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /send-receive/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /standalone/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /transactional/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /user-transaction/src/test/resources line 3 XML Problem
> cvc-pattern-valid: Value 'param1 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
> cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
> cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
> cvc-pattern-valid: Value 'param2 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
> cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
> cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
> {code}
> Additional issues:
> https://issues.jboss.org/browse/JBIDE-18352
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-19757 at 6/29/15 7:04 AM:
----------------------------------------------------------------------
reopen for clarification:
Do I read this right that the difference between optimized site and general one is at minimum 20 seconds ? That is a lifetime for a user.
But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/
was (Author: maxandersen):
reopen for clarification:
Do I read this right that the difference between optimzed site and general one is at minimum 20 seconds ? That is a lifetime for a user.
And you say we are installing *less* ...how come ? we should be installing the exact same should we not ?
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Labels: releasework
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[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:
---------------------------------------------
for me I see a and b as the clean way that just wont change and allow us to separate what content/structure we do during builds from the released updatesite.
#c is exactly what we avoid having to do by having a and b.
These names solve two different things: a/b gives stable urls for users and c should be contained within the build system. No user should have to care about this.
> 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, 10 months