September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23143: ------------------------------------ Blocked by JBIDE-22581 > Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23143 > URL: https://issues.jboss.org/browse/JBIDE-23143 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, updatesite, upstream, webservices > Affects Versions: 4.4.1.Final > Reporter: Martin Malina > Assignee: Mickael Istria > Fix For: 4.4.2.AM2 > > Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png > > > When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen. > !neon-1-remediation.png! > If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools. > This is the original error message (third option): > {code} > Your original request has been modified. > "Code Recommenders Snipmatch" will be ignored because a newer version is already installed. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) > Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824) > Only one of the following can be installed at once: > Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129) > Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824) > Cannot satisfy dependency: > From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549) > To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129] > Cannot satisfy dependency: > From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129) > To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129] > Cannot satisfy dependency: > From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824) > To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824] > Cannot satisfy dependency: > From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648) > To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0) > {code} > [1] http://download.jboss.org/jbosstools/neon/staging/updates/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23261) server New and Noteworthy for 4.4.2.AM1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23261?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-23261. ------------------------------- Resolution: Done nothing here > server New and Noteworthy for 4.4.2.AM1 > --------------------------------------- > > Key: JBIDE-23261 > URL: https://issues.jboss.org/browse/JBIDE-23261 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-23157: -------------------------------------- +1 start fresh - let;'s focus on the unresolved bugs. ;-) > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM2 > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22173) write validation tests to ensure published content has been correctly published

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22173?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22173: ------------------------------------ Code lives here for the tests to run / files to verify: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... Despite the name it works for staging and development / stable too. > write validation tests to ensure published content has been correctly published > ------------------------------------------------------------------------------- > > Key: JBIDE-22173 > URL: https://issues.jboss.org/browse/JBIDE-22173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Once we're done running stage.sh, we need a way to automatically review the content has been correctly published. > Today, we do this: > {code} > versionWithRespin=4.3.1.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${v... " >> $tmpfile > done > for site in browsersim-standalone; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > done > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > rm -fr $tmpfile > # verify changes > echo "Check 6 URLs:" > firefox \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \ > http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/ \ > http://download.jboss.org/jbosstools/mars/staging/updates/ > {code} > or > {code} > versionWithRespin=9.1.0.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in central earlyaccess discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWit... " >> $tmpfile > done > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${vers... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${ver... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_su... " >> $tmpfile > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > popd >/dev/null > rm -fr $tmpfile > # verify changes > echo "Check 4 URLs:" > firefox \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \ > https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \ > https://devstudio.redhat.com/9.0/staging/updates/ > {code} > But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published. > Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present. > May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22173) write validation tests to ensure published content has been correctly published

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22173?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22173. ------------------------------ Resolution: Done > write validation tests to ensure published content has been correctly published > ------------------------------------------------------------------------------- > > Key: JBIDE-22173 > URL: https://issues.jboss.org/browse/JBIDE-22173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Once we're done running stage.sh, we need a way to automatically review the content has been correctly published. > Today, we do this: > {code} > versionWithRespin=4.3.1.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${v... " >> $tmpfile > done > for site in browsersim-standalone; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > done > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > rm -fr $tmpfile > # verify changes > echo "Check 6 URLs:" > firefox \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \ > http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/ \ > http://download.jboss.org/jbosstools/mars/staging/updates/ > {code} > or > {code} > versionWithRespin=9.1.0.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in central earlyaccess discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWit... " >> $tmpfile > done > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${vers... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${ver... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_su... " >> $tmpfile > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > popd >/dev/null > rm -fr $tmpfile > # verify changes > echo "Check 4 URLs:" > firefox \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \ > https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \ > https://devstudio.redhat.com/9.0/staging/updates/ > {code} > But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published. > Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present. > May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22173) write validation tests to ensure published content has been correctly published

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22173?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22173: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.x) > write validation tests to ensure published content has been correctly published > ------------------------------------------------------------------------------- > > Key: JBIDE-22173 > URL: https://issues.jboss.org/browse/JBIDE-22173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Once we're done running stage.sh, we need a way to automatically review the content has been correctly published. > Today, we do this: > {code} > versionWithRespin=4.3.1.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${v... " >> $tmpfile > done > for site in browsersim-standalone; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > done > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > rm -fr $tmpfile > # verify changes > echo "Check 6 URLs:" > firefox \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \ > http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/ \ > http://download.jboss.org/jbosstools/mars/staging/updates/ > {code} > or > {code} > versionWithRespin=9.1.0.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in central earlyaccess discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWit... " >> $tmpfile > done > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${vers... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${ver... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_su... " >> $tmpfile > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > popd >/dev/null > rm -fr $tmpfile > # verify changes > echo "Check 4 URLs:" > firefox \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \ > https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \ > https://devstudio.redhat.com/9.0/staging/updates/ > {code} > But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published. > Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present. > May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22173) write validation tests to ensure published content has been correctly published

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22173?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22173: ------------------------------------ Verification tests are now codified here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... > write validation tests to ensure published content has been correctly published > ------------------------------------------------------------------------------- > > Key: JBIDE-22173 > URL: https://issues.jboss.org/browse/JBIDE-22173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Once we're done running stage.sh, we need a way to automatically review the content has been correctly published. > Today, we do this: > {code} > versionWithRespin=4.3.1.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${v... " >> $tmpfile > done > for site in browsersim-standalone; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${ver... " >> $tmpfile > done > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > rm -fr $tmpfile > # verify changes > echo "Check 6 URLs:" > firefox \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \ > http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \ > http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \ > http://download.jboss.org/jbosstools/mars/staging/updates/core/ \ > http://download.jboss.org/jbosstools/mars/staging/updates/ > {code} > or > {code} > versionWithRespin=9.1.0.CR1b # a, b, c... > tmpfile=/tmp/jbosstools-staging__verify.txt > for site in central earlyaccess discovery.central discovery.earlyaccess; do > if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWit... " >> $tmpfile > done > echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRe... " >> $tmpfile > echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${vers... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${ver... " >> $tmpfile > echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_su... " >> $tmpfile > echo "" >> $tmpfile > cat $tmpfile > firefox `cat $tmpfile` > popd >/dev/null > rm -fr $tmpfile > # verify changes > echo "Check 4 URLs:" > firefox \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \ > https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \ > https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \ > https://devstudio.redhat.com/9.0/staging/updates/ > {code} > But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published. > Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present. > May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-424) ClassCastException in JSONModelParser.insertValue [EBZ#502183]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-424: --------------------------------------- Summary: ClassCastException in JSONModelParser.insertValue [EBZ#502183] Key: ERT-424 URL: https://issues.jboss.org/browse/ERT-424 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot The following problem was reported via the automated error reporting: Message: org.eclipse.wst.json.core.internal.document.JSONDocumentImpl cannot be cast to org.eclipse.wst.json.core.internal.document.JSONPairImpl java.lang.ClassCastException: org.eclipse.wst.json.core.internal.document.JSONDocumentImpl cannot be cast to org.eclipse.wst.json.core.internal.document.JSONPairImpl at org.eclipse.wst.json.core.internal.document.JSONModelParser.insertValue(JSONModelParser.java:904) at org.eclipse.wst.json.core.internal.document.JSONModelParser.insertStructuredDocumentRegion(JSONModelParser.java:854) at org.eclipse.wst.json.core.internal.document.JSONModelParser.replaceStructuredDocumentRegions(JSONModelParser.java:1706) at org.eclipse.wst.json.core.internal.document.JSONModelImpl.handleRefresh(JSONModelImpl.java:411) at org.eclipse.wst.json.core.internal.document.JSONModelImpl.nodesReplaced(JSONModelImpl.java:599) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:600) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1198) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1979) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:103) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1094) at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1119) at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:625) at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:233) at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7374) at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8225) at org.eclipse.swt.custom.StyledText.doContent(StyledText.java:2530) at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:6018) at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:6049) at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5733) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) Bundles: | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | | org.eclipse.jface.text | 3.11.0.v20160505-1301 | 3.11.0.v20160505-1301 | | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 | | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | | org.eclipse.wst.json.core | 1.0.100.v201608161657 | 1.0.100.v201608161657 | | org.eclipse.wst.sse.core | 1.1.1000.v201608061824 | 1.1.1000.v201608061824 | | org.eclipse.wst.sse.ui | 1.3.500.v201605120129 | 1.3.500.v201605120129 | Operating Systems: | Windows | 6.3.0 | 6.3.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57dd6... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. Created on behalf of vrubezhny(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23157 at 9/26/16 12:20 PM: -------------------------------------------------------------- Oh, and should we move issues out of the "common/jst/core" bucket into the new jst component? If so I'll need some way of identify such issues as being different from "common" or "foundation" components. There are 42 unresolved issues for the existing component: https://issues.jboss.org/issues/?jql=component%20%3D%20%22common%2Fjst%2F... There are also 807 resolved issues. Maybe it would be better to create a NEW "common" component, and archive the old one? That way we won't need to figure out how to move 849 issues around. :D was (Author: nickboldt): Oh, and should we move issues out of the "common/jst/core" bucket into the new jst component? If so I'll need some way of identify such issues as being different from "common" or "foundation" components. There are 42 unresolved issues for the existing component: https://issues.jboss.org/issues/?jql=component%20%3D%20%22common%2Fjst%2F... > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM2 > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23157: ------------------------------------ Oh, and should we move issues out of the "common/jst/core" bucket into the new jst component? If so I'll need some way of identify such issues as being different from "common" or "foundation" components. There are 42 unresolved issues for the existing component: https://issues.jboss.org/issues/?jql=component%20%3D%20%22common%2Fjst%2F... > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM2 > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- 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 September 2016