June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-8) support docker ignore [EBZ#469819]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/ERT-8?page=com.atlassian.jira.plugin.syst... ] Alexey Kazakov updated ERT-8: ----------------------------- Sprint: (was: devex #115 May 2016) > support docker ignore [EBZ#469819] > ---------------------------------- > > Key: ERT-8 > URL: https://issues.jboss.org/browse/ERT-8 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > it does not look like docker build from eclipse honors .dockerignore > which makes its builds much slower for projects that contain source and other artifacts. > example with project using .dockerignore https://github.com/jbosstools/jbosstools-website -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-8) support docker ignore [EBZ#469819]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/ERT-8?page=com.atlassian.jira.plugin.syst... ] Alexey Kazakov updated ERT-8: ----------------------------- Fix Version/s: Neon.1 (4.6) (was: Neon (4.6)) > support docker ignore [EBZ#469819] > ---------------------------------- > > Key: ERT-8 > URL: https://issues.jboss.org/browse/ERT-8 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > it does not look like docker build from eclipse honors .dockerignore > which makes its builds much slower for projects that contain source and other artifacts. > example with project using .dockerignore https://github.com/jbosstools/jbosstools-website -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3942) Document (and verify) the current operation of the platform installer

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3942: ---------------------------------- Summary: Document (and verify) the current operation of the platform installer Key: JBDS-3942 URL: https://issues.jboss.org/browse/JBDS-3942 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.0.0.GA Reporter: Len DiMaggio Priority: Critical Fix For: 10.0.0.GA We have to be careful to test and document the operation of the installer for the release: Component detection as performed that the bundled platform installer has recently changed. It's important that we communicate clearly to our users how this detection is functioning as of today, and what their options are for running the installer. The installer installs these (6) high-level components: * CDK * Cygwin * VirtialBox * Vagrant * JDK * DevStudio Topic: Component Detection Performed by The Installer: As of today, the installer is able to detect these components: * Java * VirtualBox * Vagrant If a user runs the installer, and one of these detectable components is installed, the installer will verify that the version of the installed component is supported by the Developer Platform. If the version of the detected component installed is not supported, an error will be reported to the user. The installer will not automatically update the detected installed component to a supported version. If the version of the installed component is supported by the Developer Platform, the installer will not overwrite that installed component. Topic: Components Auto-Selected by the Installer If the installer is run on a system with none of the high level components pre-installed, the installer should have all components auto-selected to be installed. Topic: Optionally Installing Components As of today, users can choose to install selected components singly with the installer. The only dependency should be that if the user attempts to install DevStudio alone, the installer will require the user to also install the JDK at the same time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22305: ------------------------------------ Jenkins job is running and working. * TODO: generate email notification including link to jenkins job, diff files, and associated JIRA(s), plus instructions for how to build the TP locally. > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.1.Alpha1 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.0.Final) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.1.Alpha1 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3941) use new logo in UI of Development Suite installer

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Catherine Robson commented on JBDS-3941: ---------------------------------------- [~nickboldt] can you provide Denis the .ico file that we use for JBDS 5-9? > use new logo in UI of Development Suite installer > ------------------------------------------------- > > Key: JBDS-3941 > URL: https://issues.jboss.org/browse/JBDS-3941 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: installer-new-logo-confirmation.png, installer-new-logo-login.png, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3909) rebrand dev platform installer as Red Hat Development Suite

by SJ Cox (JIRA)

[ https://issues.jboss.org/browse/JBDS-3909?page=com.atlassian.jira.plugin.... ] SJ Cox commented on JBDS-3909: ------------------------------ [~dgolovin] What is the dimension of the Red Hat Developer logo in the top right corner? I will supply you with a new logo without the red brackets. Thanks! > rebrand dev platform installer as Red Hat Development Suite > ----------------------------------------------------------- > > Key: JBDS-3909 > URL: https://issues.jboss.org/browse/JBDS-3909 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Attachments: RH_DevelopmentSuite_Logo.svg, updated-branding.png > > > Per decision made last week in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo and https://docs.google.com/presentation/d/1Ub-egAS7nbzFijKCTnUk7GJP8WPCQC28q... we need to refactor the platform installer to be the Development Suite installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3941) use new logo in UI of Development Suite installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3941?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3941: ------------------------------------- Logo we currently use is here https://github.com/redhat-developer-tooling/developer-platform-install/bl... I guess we also need a new .ico file which is here https://github.com/redhat-developer-tooling/developer-platform-install/bl... > use new logo in UI of Development Suite installer > ------------------------------------------------- > > Key: JBDS-3941 > URL: https://issues.jboss.org/browse/JBDS-3941 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Catherine Robson > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: installer-new-logo-confirmation.png, installer-new-logo-login.png, RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22577) Import wizard: InterruptedException if I cancel the job

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22577?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22577: ------------------------------------------ Fix Version/s: 4.4.1.Alpha1 > Import wizard: InterruptedException if I cancel the job > ------------------------------------------------------- > > Key: JBIDE-22577 > URL: https://issues.jboss.org/browse/JBIDE-22577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: import_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1, 4.4.x > > Attachments: import-interrupted-exception.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2044: ---------------------------------- "does this mean devstudio since 2012 have been reporting itself as eclipse platform and not devstudio ?" Yes, that would be my assumption based on Denis' writeup from 4 years ago. :D > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.1.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016