[JBoss JIRA] (JBDS-3264) Remove welcome/intro page
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3264?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3264:
--------------------------------------
[~maxandersen] [~mmurray] I let you decide whether this is worth keeping the JBDS intro page (the red and white one with only a link saying "Get started with JBoss Central"). The PR only has to be rebased and merged.
> Remove welcome/intro page
> -------------------------
>
> Key: JBDS-3264
> URL: https://issues.jboss.org/browse/JBDS-3264
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: ui/branding
> Affects Versions: 8.0.0.GA
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Optional
> Fix For: 9.0.0.Beta2
>
>
> The welcome page for JBDS is really useless. It doesn't provide any value to the user. Moreover, it looks quite old-fashioned.
> In such case, it would be better to remove it and prevent users from seeing it.
--
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 Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20141:
---------------------------------------------
I don't follow what you mean with index copied or symlinked. The html should just say something like "This is updatesite for JBoss Tools snapshot/development/release".
What content is it that you expect to be needing accurate/current ? The list of features/bundles ? just listing the one from from jboss tools core would not be correct anyway - it would just show what is in the raw core site. I thought you said you wanted the core raw site to be browsable so you could navigate it to more easy check its content ?
> 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] (JBDS-3477) Launching with Java 7 in jbdevstudio.ini results in module errors in subsequent launches with Java 8
by Jan Richter (JIRA)
Jan Richter created JBDS-3477:
---------------------------------
Summary: Launching with Java 7 in jbdevstudio.ini results in module errors in subsequent launches with Java 8
Key: JBDS-3477
URL: https://issues.jboss.org/browse/JBDS-3477
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 9.0.0.Beta1
Reporter: Jan Richter
Attachments: warning.png
When I launch JBDS with the -vm parameter in jbdevstudio.ini set to Java 7 and then try to launch it again with Java 8, I get a warning that a number of modules failed to load.
The stated reason is they cannot be loaded with Java 8 because they require Java 8.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20167) Openshift Tooling Usage Tracking
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20167?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20167:
---------------------------------------------
[~burrsutter] not sure which part we should/could track sensibly.
Record when someone setups up a new connection and track which type (v2 or v3) they make and/or if the connection was for default address or not ? Then we can know if on-premise or online without recording the actual ip/hostname.
That would match what we do for server adapters where we know how often a server is made and of what type/version.
[~adietish] this is pretty trivial to add and gives valuable information. See https://github.com/jbosstools/jbosstools-devdoc/blob/master/api/usage/usa... - [~akazakov] can help if questions.
> Openshift Tooling Usage Tracking
> --------------------------------
>
> Key: JBIDE-20167
> URL: https://issues.jboss.org/browse/JBIDE-20167
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Labels: usage
> Fix For: 4.3.0.CR1
>
>
> Embed usage tracking logic in the Openshift v3 tooling - allowing us to know how many individuals are using those tools.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months