May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by SJ Cox (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] SJ Cox commented on JBDS-3605: ------------------------------ [~nickboldt] Attached are the revised icons at the correct dimensions. Let me know if these work for you, thanks! [^RevisedIcons.zip] > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, Additional_RHDS_Branding.zip, edit-eap-icon-in-ds10-installer.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, RevisedIcons.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-607) Validate IS URLs

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-607?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-607. ---------------------------- Fix Version/s: 9.0.1.GA Resolution: Done Added test infrastructure to validate IS specific p2 repos and update sites. > Validate IS URLs > ---------------- > > Key: JBTIS-607 > URL: https://issues.jboss.org/browse/JBTIS-607 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > > There exists staging, integration, development and stable URLs in support of p2 installations as well as JBoss Central. We need an automated way of validating that a defined list of URLs is consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-607) Validate IS URLs

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-607?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-607 at 5/16/16 4:02 PM: ----------------------------------------------------------- Added code borrowed from Max to verify a list of integration-stack specific p2 update/ ref sites as well as those defined by ide-config.properties. https://github.com/jbosstools/jbosstools-integration-stack/commit/91e9d12... was (Author: pleacu): I'm building this now via Jenkins on-demand: https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.1-... Should we close this Jira and create new ones on how we'd like to modify what we now have? > Validate IS URLs > ---------------- > > Key: JBTIS-607 > URL: https://issues.jboss.org/browse/JBTIS-607 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > There exists staging, integration, development and stable URLs in support of p2 installations as well as JBoss Central. We need an automated way of validating that a defined list of URLs is consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- I'm building this now via Jenkins on-demand: https://devstudio.redhat.com/9.0/staging/updates/integration-stack/9.0.1-... Should we close this Jira and create new ones on how we'd like to modify what we now have? > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21657: ------------------------------------ Well, for the case of the server job, I can only see artifacts for the current build, plus the two successful blue jobs. It's unclear why artifacts were not stored for any of the yellow or red jobs, since "Archive artifacts only if build is successful" is unchecked. Re: your comment about not wanting a "Swiss Army knife" solution for both PRs and commits, to me it seems easier to have one job config that works for both. Either you... * run 3 steps ** (build commit, ** deploy update site onto download.jboss.org (with automated cleanup) in a /builds/ folder, ** run tests) or you... * run 3 steps ** (build PR, ** deploy PR update site onto download.jboss.org (with automated cleanup) in a /pulls/ folder, ** run tests) Why make the config different for a PR vs. a commit, when both uscases can do the same steps and thus keep things simpler? > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3787: ----------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3787: -------------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3787: -------------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3787: ----------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3787: -------------------------------- > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016