[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20141:
-------------------------------
Description:
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.
was:
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/
----
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/
> 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
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20141:
------------------------------------
So... I propose a few things:
a) remove both updates/nightly/* symlinks; update any references to these URLs on tools.jboss.org
b) remove all updates/development/mars/ symlink; update any references to these URLs on tools.jboss.org
c) consider publishing the contents of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... into http://download.jboss.org/jbosstools/mars/snapshots/updates/ since that is the composite site containing 4 child sites: JBT, JBT TP, Central, Central TP. *HOWEVER*, once we flip over to using the jbosstools-4.3.x branch for stable builds, this publishing step would need to change so that the bits would come from the discovery.central_4.3.mars job instead of the _master one; then _master would go to /neon/snapshots/updates/ [1]
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=453927#c137
> 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/
> ----
> 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/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18274:
---------------------------------------
OK, so this is my java file:
{code}
package javaproj;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.net.MalformedURLException;
import java.net.URL;
import java.net.HttpURLConnection;
import java.net.URLConnection;
public class ServerCheck {
public static void main(String[] args) {
// TODO Auto-generated method stub
if(onePing("http://nattura.brq.redhat.com:8080")) {
System.out.println("true");
}
else {
System.out.println("false");
}
}
private static boolean onePing(String url) {
URLConnection conn = null;
try {
URL pingUrl = new URL(url);
conn = pingUrl.openConnection();
((HttpURLConnection)conn).getResponseCode();
return true;
} catch( FileNotFoundException fnfe ) {
return true;
} catch (MalformedURLException e) {
// Should NEVER happen since the URL's are hand-crafted, but whatever
//Status s = new Status(IStatus.ERROR, JBossServerCorePlugin.PLUGIN_ID, e.getMessage(), e);
//JBossServerCorePlugin.getDefault().log(s);
} catch (IOException e) {
// Does not need to be logged
return false;
} finally {
if( conn != null ) {
((HttpURLConnection)conn).disconnect();
}
}
return false;
}
}
{code}
And it returns true. And yet, the server view is in "Starting" status.
The steps to reproduce are still the same. I tried this today with JBDS 9.0.0.Beta1, WildFly 8.2, Oracle JDK 1.7, OS X 10.10 Yosemite. As the steps describe, this server is created using runtime detection, so naturally it's using the Local server mode.
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20141:
-------------------------------
Description:
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/
----
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/
was:
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.
> 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/
> ----
> 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/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-20141:
----------------------------------
Summary: 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
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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months