July 2015 - jbosstools-issues - Jboss List Archives

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19598: ---------------------------------------- [~maxandersen] Does the buildchow have support for this Jenkins plugin? > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-636) JBDS-IS: Create a FAQ article and add to the splash page

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-636?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-636: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr), 08-Jun -> 21-Jun 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 2015/S8 (13-Apr > 26-Apr), 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT) > JBDS-IS: Create a FAQ article and add to the splash page > -------------------------------------------------------- > > Key: TOOLSDOC-636 > URL: https://issues.jboss.org/browse/TOOLSDOC-636 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create a frequently asked questions article and add it to the splash page for JBDS-IS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-615) Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-615?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-615: ------------------------------- Sprint: 08-Jun -> 21-Jun 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT) > Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0 > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-615 > URL: https://issues.jboss.org/browse/TOOLSDOC-615 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Getting Started Guide > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > > Requirements: > * Use the current Start Developing Guide to test content > * Review contents and determine if this would be better as a new series of articles rather than a document for 9.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20175) JBT update site returns 404 Not Found

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20175?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20175: --------------------------------------------- As discussed in JBIDE-20141 there is still some mismatch between the urls so for now I've rolled this back to what we used the first 6 months: http://download.jboss.org/jbosstools/updates/nightly/mars/ once the repo location discussed at JBIDE-20141 has been settled so we don't move this again back and forth we can update. > JBT update site returns 404 Not Found > ------------------------------------- > > Key: JBIDE-20175 > URL: https://issues.jboss.org/browse/JBIDE-20175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: page.png > > > The JBT nightly update site http://download.jboss.org/jbosstools/mars/development/nightly does not point to a valid repository and returns code 404 Not found. This URL is listed on the JBT Downloads page > http://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Nightly.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-647) Update JBDS 9.0.0 Install doc with info for offline zip

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-647?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-647: ------------------------------- Sprint: 06-Jul >> 19-Jul 2015-JBDS/JBT (was: 22-Jun >> 05-Jul 2015-JBDS/JBT) > Update JBDS 9.0.0 Install doc with info for offline zip > ------------------------------------------------------- > > Key: TOOLSDOC-647 > URL: https://issues.jboss.org/browse/TOOLSDOC-647 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.3.0.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > Change info in the Install JBoss Developer Studio BYOE when Offline section of the JBDS 9.0.0 Install guide to say that the user will need only one .zip (update archive) to install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[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)

[ https://issues.jboss.org/browse/JBDS-3477?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3477: ------------------------------ Attachment: warning.png > 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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2015