October 2016 - jbosstools-issues - Jboss List Archives

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23303?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-23303. ------------------------------ Reopen auto action set in aeri in case the problem still persist in new version. Closing. > 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 > Fix For: 4.4.2.AM2 > > > 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 (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23304) NullPointerException in TagLibraryManager.getStaticTLD

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23304?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-23304. ------------------------------ I've set reopen auto action in aeri in case the problem appears again. Closing. > NullPointerException in TagLibraryManager.getStaticTLD > ------------------------------------------------------ > > Key: JBIDE-23304 > URL: https://issues.jboss.org/browse/JBIDE-23304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Reporter: Automated Error Reporting Bot > Assignee: Victor Rubezhny > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:101) > at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44) > at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135) > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getLibraries(TagLibraryManager.java:57) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillXMLNamespacesForNode(PageContextFactory.java:1166) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForNode(PageContextFactory.java:869) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForChildNodes(PageContextFactory.java:858) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:602) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:403) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:392) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:381) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:299) > 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.core.resources | 3.10.1.v20150725-1910 | 3.10.1.v20150725-1910 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | > | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.6.201.v20150819-1034 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.eclipse.wst.validation.ui | 1.2.500.v201310231452 | 1.2.500.v201310231452 | > | org.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.501.v201501212057 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160624-2216 | > | org.jboss.tools.jsf.ui | 3.7.1.Final-v20160330-2256-B84 | 3.7.1.Final-v20160330-2256-B84 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160829-2118 | > | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 | > Operating Systems: > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574c32dae4b06056d2...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21198. ------------------------------ F3 now opens User.java. But there is still this issue: https://issues.jboss.org/browse/JBIDE-21201. Closing this one. > "Tern - Go to definition" hyperlink opens nothing > ------------------------------------------------- > > Key: JBIDE-21198 > URL: https://issues.jboss.org/browse/JBIDE-21198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150912-1100-B100 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.1.Final > > > 1. Install AngularJS from JBoss Central (Enable Early Access) > 2. Create JSF 1.2 Kick Start project > 3. Open inputUserName.jsp in VPE > 4. Click on 'user' text within <h:inputText> tag > 5. Press F3 key > ERROR: Nothing happened. User.java file should be opened in editor > 6. Hover with mouse over the same text and push Ctrl key > ASSERT: Menu with these tree actions appeared: > * Tern - Go to definiton > * Open User.java > * Open 'User - demo' > Action Open User.java opens User.java in editor -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4133) Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-4133: -------------------------------------- {quote}Hopefully this will fix things:{quote} It made the rpm uninstallable - JBDS-4141 > Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+ > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-4133 > URL: https://issues.jboss.org/browse/JBDS-4133 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > Snippet from log attached to JBDS-4131: > {code} > !ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-21 14:55:03.519 > !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477058103380-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629 > !STACK 0 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} > And > {code} > !ENTRY org.eclipse.help.base 4 0 2016-10-21 14:32:21.719 > !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610121400 [389]. Please use an index built with Lucene 5 or higher. > {code} > then 100s of errors like this: > {code} > !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_preferencePages.html cannot be opened. > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4141) RPM requires lucene3 -> not installable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4141?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4141: --------------------------------- Fix Version/s: 10.2.0.AM3 > RPM requires lucene3 -> not installable > --------------------------------------- > > Key: JBDS-4141 > URL: https://issues.jboss.org/browse/JBDS-4141 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > > The latest builds of rh-eclipse46-devstudio.rpm (e.g. rh-eclipse46-devstudio-10.2-0.20161026.0012.el7) don't install. They require lucene3 which isn't provided on RHEL 7.2+. The only available lucene packages seem to be rh-java-common-lucene (4.8) and rh-java-common-lucene5 (5.4) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4141) RPM requires lucene3 -> not installable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4141?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-4141: ------------------------------------ Assignee: Nick Boldt > RPM requires lucene3 -> not installable > --------------------------------------- > > Key: JBDS-4141 > URL: https://issues.jboss.org/browse/JBDS-4141 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > > The latest builds of rh-eclipse46-devstudio.rpm (e.g. rh-eclipse46-devstudio-10.2-0.20161026.0012.el7) don't install. They require lucene3 which isn't provided on RHEL 7.2+. The only available lucene packages seem to be rh-java-common-lucene (4.8) and rh-java-common-lucene5 (5.4) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4141) RPM requires lucene3 -> not installable

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4141?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4141: --------------------------------- Priority: Blocker (was: Major) > RPM requires lucene3 -> not installable > --------------------------------------- > > Key: JBDS-4141 > URL: https://issues.jboss.org/browse/JBDS-4141 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Priority: Blocker > > The latest builds of rh-eclipse46-devstudio.rpm (e.g. rh-eclipse46-devstudio-10.2-0.20161026.0012.el7) don't install. They require lucene3 which isn't provided on RHEL 7.2+. The only available lucene packages seem to be rh-java-common-lucene (4.8) and rh-java-common-lucene5 (5.4) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23390) fix staging repo id for pushing releases to jboss nexus

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23390?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23390. -------------------------------- Verified in git. Changes have been commited to: jbosstools-build - master jbosstools-build-ci - jbosstools-4.4.x jbosstools-maven-plugins - master bosstools-target-platforms - 4.60.x bosstools-target-platforms - 4.61.x > fix staging repo id for pushing releases to jboss nexus > ------------------------------------------------------- > > Key: JBIDE-23390 > URL: https://issues.jboss.org/browse/JBIDE-23390 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, maven, target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Last night when trying to release jbosstools-maven-plugins I was given this error: > {code} > ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy > (default-deploy) on project tycho-plugins: Failed to deploy artifacts: > Could not transfer artifact org.jboss.tools:tycho-plugins:pom:0.26.0 > from/to jboss-staging-repository > (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/): > Failed to transfer file: > https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/or.... > Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]{code} > Turns out the solution is this change: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/31662dca8a6... > So, we should roll this out to the parent pom, target platforms root pom, and jbosstools-build-ci too. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-959) Create test for RHBPMS-4302

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-959: --------------------------------- Summary: Create test for RHBPMS-4302 Key: JBTIS-959 URL: https://issues.jboss.org/browse/JBTIS-959 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.4.0.CR1-TP Reporter: Jozef Marko Assignee: Jozef Marko Create test that will verify if signall event created in jbpm-designer can be saved after import into bpmn2 modeler. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-814) Fuse - Extend the scope of projects used for testing deployment/undeployment

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-814?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-814: ------------------------------- Summary: Fuse - Extend the scope of projects used for testing deployment/undeployment (was: Extend the scope of projects used for testing deployment/undeployment) > Fuse - Extend the scope of projects used for testing deployment/undeployment > ---------------------------------------------------------------------------- > > Key: JBTIS-814 > URL: https://issues.jboss.org/browse/JBTIS-814 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.3.1.Final > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Extend the scope of projects used for testing deployment/undeployment. It seems that projects which were imported a an existing maven project cannot be successfully deployed/undeployed. Please see FUSETOOLS-1997 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 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