June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22579) Replace assertion in AbstractExporterFacade.setOutput() and in AbstractExporterFacade.setCustopProperties() by condition

by Koen Aers (JIRA)

Koen Aers created JBIDE-22579: --------------------------------- Summary: Replace assertion in AbstractExporterFacade.setOutput() and in AbstractExporterFacade.setCustopProperties() by condition Key: JBIDE-22579 URL: https://issues.jboss.org/browse/JBIDE-22579 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Priority: Critical Fix For: 4.4.x This code fails when running with JDK 8. -- 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 edited comment on JBIDE-22305 at 6/9/16 12:10 AM: ------------------------------------------------------------- I have created a job that will run changeTargetURLs.sh [2] However, because the upstrem Neon.0.RC4 mirror job is failing [1], so too is the TP change verify job [2], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: [~mickael_istria] [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... was (Author: nickboldt): I have created a job that will run changeTargetURLs.sh [1] However, because the upstrem Neon.0.RC4 mirror job is failing, so too is the TP change verify job [2], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: [~mickael_istria] [] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > 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.0.Final > > > 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 edited comment on JBIDE-22305 at 6/9/16 12:09 AM: ------------------------------------------------------------- I have created a job that will run changeTargetURLs.sh. However, because the upstrem Neon.0.RC4 mirror job is failing, so too is the TP change verify job [4], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: [~mickael_istria] [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [4] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... was (Author: nickboldt): I have created a job that will run changeTargetURLs.sh. However, because the upstrem Neon.0.RC4 mirror job is failing, so too is the TP change verify job [4], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: Mickael Istria Ref: JBIDE-22305 [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [4] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > 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.0.Final > > > 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 edited comment on JBIDE-22305 at 6/9/16 12:09 AM: ------------------------------------------------------------- I have created a job that will run changeTargetURLs.sh [1] However, because the upstrem Neon.0.RC4 mirror job is failing, so too is the TP change verify job [2], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: [~mickael_istria] [] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... was (Author: nickboldt): I have created a job that will run changeTargetURLs.sh. However, because the upstrem Neon.0.RC4 mirror job is failing, so too is the TP change verify job [4], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: [~mickael_istria] [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [4] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > 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.0.Final > > > 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-22438) Ensure Jetty version in Neon.0.RC3/4 is compatible with JBoss Tools components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22438?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22438: ------------------------------------ Yes, looks like livereload, cordovasim and browsersim will need to update their poms/manifests to support Jetty 9.3.9, once the updated RC4 target platform is avaialble tomorrow. cc: [~ibuziuk] [~xcoulon] --- I'm currently attempting to mirror it but the Jenkins job has crapped out 3 times so far so I'm mirroring it the old way and hoping that 2-4hr process won't die after only about 25% is mirrored. Meanwhile I've at least pulled a new Jetty 9.3.9 [1] mirror [2]. [1] http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.9.v20160517/ [2] http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.9.v20... However, because the mirror job is failing, so too is the TP change verify job [4], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: [~mickael_istria] Ref: JBIDE-22305 [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [4] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Ensure Jetty version in Neon.0.RC3/4 is compatible with JBoss Tools components > ------------------------------------------------------------------------------ > > Key: JBIDE-22438 > URL: https://issues.jboss.org/browse/JBIDE-22438 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: aerogear-hybrid, browsersim, cordovasim, livereload > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.4.0.Final > > > Affected projects: > jbosstools-browsersim, jbosstools-aerogear, jbosstools-livereload -- 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: ------------------------------------ I have created a job that will run changeTargetURLs.sh. However, because the upstrem Neon.0.RC4 mirror job is failing, so too is the TP change verify job [4], so the git diff for the TP change is incomplete, showing ONLY the URL changes and not the IU changes. cc: Mickael Istria Ref: JBIDE-22305 [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... [4] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > 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.0.Final > > > 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-3889) Remove JBoss from Platform Installer full name

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3889?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3889: ---------------------------------- Note that this decision was later amended so that the platform installer is now called Red Hat Development Suite. > Remove JBoss from Platform Installer full name > ---------------------------------------------- > > Key: JBDS-3889 > URL: https://issues.jboss.org/browse/JBDS-3889 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha2 > > > Platform installer full name is "Red Hat Developer Studio Platform Installer" and it should be updated in many places throughout Plafrom Installer: > 1. Banner > 2. Window title > 3. Confirmation page Dev Studio name > 4. Start up page Dev Studio name > 5. Exec file "Details" tab info > 6. Target install folder name (see JBDS-3874) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3936) devstudio.exe has eclipse icon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3936?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3936: ----------------------------- Sprint: devex #115 May 2016 > devstudio.exe has eclipse icon > ------------------------------ > > Key: JBDS-3936 > URL: https://issues.jboss.org/browse/JBDS-3936 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 10.0.0.GA > > Attachments: devstudio.ico.10.png, jbds.ico.9.1.png, jbds.ico.9.1export-layers.png, jbds.ico_vs_devstudio.ico.png > > > [installFolder]/studio/devstudio.exe has eclipse icon instead of redhat developer icon. > http://i.imgur.com/ZKjeJGC.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for devstudio 10.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3606: ----------------------------- Fix Version/s: 10.0.0.GA (was: 10.0.0.Alpha2) > update branding for devstudio 10.0 installer > -------------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: James Cobb > Fix For: 10.0.0.GA > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for devstudio 10.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3606: ----------------------------- Sprint: devex #114 May 2016, devex #115 May 2016 (was: devex #114 May 2016) > update branding for devstudio 10.0 installer > -------------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: James Cobb > Fix For: 10.0.0.GA > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- 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