October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3754) Installer: redirect links for Vagrant and VirtualBox should use https

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3754?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3754: -------------------------------- Comment: was deleted (was: Cannot replicate this because format validation kick is an reports that path has wrong format.) > Installer: redirect links for Vagrant and VirtualBox should use https > --------------------------------------------------------------------- > > Key: JBDS-3754 > URL: https://issues.jboss.org/browse/JBDS-3754 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.2.0.AM2 > > > Installer's requirements.json file \[1] declares location of Vagrant and VirtualBox installers like these: > {code} > http://developers.redhat.com/redirect/to/vagrant-1.7.4.download > http://developers.redhat.com/redirect/to/virtualbox-5.0.8.download > {code} > They should use *https* scheme. > \[1] https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22850 at 10/7/16 2:51 PM: ------------------------------------------------------------- Tests: {code} python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM2 -d 10.2.0.AM2 python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.Final -d 10.2.0.GA python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM2 -d 10.7.0.AMz python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.7.AMz -d 10.7.0.AMz python findlostpatches.py -u nickboldt -p PWD -s https://issues.stage.jboss.org -b master -i 4.4.2.AM1 -d 10.7.0.AM1 -t "foo" python findlostpatches.py -u nickboldt -p PWD -s https://issues.stage.jboss.org -b master -i 4.4.7.AMr -d 11.0.0.que -t "foo" python createTestFailureJIRA.py -j https://issues.stage.jboss.org -k nickboldt -l PWD -t \ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_41... -u nickboldt -v "PWD" -c server -a 4.4.7.AMr python createTaskJIRAs.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.7.AM3 -d 11.0.0.AM1 -t "foo" python createTaskJIRAs.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM3 -d 11.0.0.AM1 -t "foo" {code} was (Author: nickboldt): Tests: {code} python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM2 -d 10.2.0.AM2 python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.Final -d 10.2.0.GA python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM2 -d 10.7.0.AMz python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.7.AMz -d 10.7.0.AMz python findlostpatches.py -u nickboldt -p PWD -s https://issues.stage.jboss.org -b master -i 4.4.2.AM1 -d 10.7.0.AM1 -t "foo" python findlostpatches.py -u nickboldt -p PWD -s https://issues.stage.jboss.org -b master -i 4.4.7.AMr -d 11.0.0.que -t "foo" python createTestFailureJIRA.py -j https://issues.stage.jboss.org -k nickboldt -l PWD -t https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_41... -u nickboldt -v "PWD" -c server -a 4.4.7.AMr python createTaskJIRAs.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.7.AM3 -d 11.0.0.AM1 -t "foo" python createTaskJIRAs.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM3 -d 11.0.0.AM1 -t "foo" {code} > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22850: ------------------------------------ Tests: {code} python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM2 -d 10.2.0.AM2 python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.Final -d 10.2.0.GA python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM2 -d 10.7.0.AMz python createnewandnoteworthy.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.7.AMz -d 10.7.0.AMz python findlostpatches.py -u nickboldt -p PWD -s https://issues.stage.jboss.org -b master -i 4.4.2.AM1 -d 10.7.0.AM1 -t "foo" python findlostpatches.py -u nickboldt -p PWD -s https://issues.stage.jboss.org -b master -i 4.4.7.AMr -d 11.0.0.que -t "foo" python createTestFailureJIRA.py -j https://issues.stage.jboss.org -k nickboldt -l PWD -t https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_41... -u nickboldt -v "PWD" -c server -a 4.4.7.AMr python createTaskJIRAs.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.7.AM3 -d 11.0.0.AM1 -t "foo" python createTaskJIRAs.py -s https://issues.stage.jboss.org -u nickboldt -p PWD -i 4.4.2.AM3 -d 11.0.0.AM1 -t "foo" {code} > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22850 at 10/7/16 2:45 PM: ------------------------------------------------------------- JBIDE-22850 #comment create new checkFixVersionsExist function in components.py, which can be reused for all 4 jira creation scripts: createTaskJIRAs.py, createTestFailureJIRA.py, createnewandnoteworthy.py, findlostpatches.py; also tweak the copy in the N&N JIRAs so they're a bit more clear, with extra links and instructions was (Author: nickboldt): create new checkFixVersionsExist function in components.py, which can be reused for all 4 jira creation scripts: > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22850: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM3) > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22850 at 10/7/16 2:40 PM: ------------------------------------------------------------- PR: https://github.com/jbosstools/jbosstools-build-ci/pull/155 tested for all four .py scripts and created a whole pile of test JIRAs on issues.stage, before deleting them. Applied in 4.4.x branch. was (Author: nickboldt): PR: https://github.com/jbosstools/jbosstools-build-ci/pull/155 > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22850: ------------------------------------ create new checkFixVersionsExist function in components.py, which can be reused for all 4 jira creation scripts: > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22850) createnewandnoteworthy should check versions provided

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22850?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22850: ---------------------------------- Assignee: Nick Boldt (was: Jeff MAURY) > createnewandnoteworthy should check versions provided > ----------------------------------------------------- > > Key: JBIDE-22850 > URL: https://issues.jboss.org/browse/JBIDE-22850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > The createnewandnoteworthy.py script should check the versions provided by the user. If an invalid version is given, then the JIRAs are created but the queries generated as part of the description are not valid, thus requiring up to 23 JIRAs to be updated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23303) NullPointerException in ELValidator.validateElOperand

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23303?page=com.atlassian.jira.plugi... ] Victor Rubezhny reassigned JBIDE-23303: --------------------------------------- Assignee: Victor Rubezhny > NullPointerException in ELValidator.validateElOperand > ----------------------------------------------------- > > Key: JBIDE-23303 > URL: https://issues.jboss.org/browse/JBIDE-23303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Reporter: Automated Error Reporting Bot > Assignee: Victor Rubezhny > > The following problem was reported via the automated error reporting: > Message: > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:513) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.1.v20160819-1517 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.jboss.tools.common.validation | 3.7.0.Final-v20150924-2213-B38 | 3.8.1.v20160624-2216 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160829-2118 | > Operating Systems: > | Linux | 3.2.0 | 4.7.0 | > | MacOSX | 10.11.5 | 10.12.0 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57221b2de4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23303) NullPointerException in ELValidator.validateElOperand

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-23303: ----------------------------------------------------- Summary: NullPointerException in ELValidator.validateElOperand Key: JBIDE-23303 URL: https://issues.jboss.org/browse/JBIDE-23303 Project: Tools (JBoss Tools) Issue Type: Bug Components: jst Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: {noformat} java.lang.NullPointerException: null at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:513) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} Bundles: | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.1.v20160819-1517 | | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 | | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | | org.jboss.tools.common.validation | 3.7.0.Final-v20150924-2213-B38 | 3.8.1.v20160624-2216 | | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160829-2118 | Operating Systems: | Linux | 3.2.0 | 4.7.0 | | MacOSX | 10.11.5 | 10.12.0 | | Windows | 6.1.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57221b2de4b0a54983...] for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 October 2016