[JBoss JIRA] (JBIDE-22906) NullPointerException in CDICoreValidator$CDIValidationContext.<init>
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22906?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-22906.
------------------------------------
verified in git & added Auto Action in aeri to open a new bug report if it happens again
> NullPointerException in CDICoreValidator$CDIValidationContext.<init>
> --------------------------------------------------------------------
>
> Key: JBIDE-22906
> URL: https://issues.jboss.org/browse/JBIDE-22906
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator$CDIValidationContext.<init>(CDICoreValidator.java:166)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.getCDIContext(CDICoreValidator.java:212)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:333)
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:140)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:77)
> at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:768)
> at org.eclipse.wst.validation.Validator.validate(Validator.java:405)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at org.eclipse.wst.validation.internal.ValidationRunner.run(ValidationRunner.java:148)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:67)
> at org.eclipse.wst.validation.ValidationFramework.validate(ValidationFramework.java:661)
> at org.eclipse.wst.sse.ui.internal.preferences.ui.AbstractValidationSettingsPage$ValidateJob.run(AbstractValidationSettingsPage.java:411)
> 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.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> Operating Systems:
> | Linux | 3.13.0 | 4.6.0 |
> | MacOSX | 10.11.4 | 10.11.5 |
> | 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/57179472e4b032f683...] 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, 7 months
[JBoss JIRA] (JBIDE-22903) NullPointerException in CDIUtil.collectAdditionalInterceptorBindingDeclaratios
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22903?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-22903.
------------------------------------
verified in git & added Auto Action in aeri to open a new bug report if this happens again
> NullPointerException in CDIUtil.collectAdditionalInterceptorBindingDeclaratios
> ------------------------------------------------------------------------------
>
> Key: JBIDE-22903
> URL: https://issues.jboss.org/browse/JBIDE-22903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message:
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114)
> at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118)
> at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641)
> at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | 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.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> Operating Systems:
> | Linux | 3.16.0 | 4.4.9.fc23 |
> | MacOSX | 10.11.4 | 10.11.6 |
> | 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/5719de0ce4b04d6a2b...] 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, 7 months
[JBoss JIRA] (JBIDE-22657) smart import nullpointer
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22657?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22657.
-------------------------------
Couldn't reproduce this either. Since nobody complained, I'll close this as non-reproducible.
> smart import nullpointer
> ------------------------
>
> Key: JBIDE-22657
> URL: https://issues.jboss.org/browse/JBIDE-22657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.4.1.Final, 4.5.0.AM1
>
>
> when using smartimport to import https://github.com/maxandersen/imapfilter-docker.git from disk I got a NPE in jaxrs:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.internal.importer.JaxRsConfigurator.canConfigure(JaxRsConfigurator.java:66)
> at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.importProjectAndChildrenRecursively(SmartImportJob.java:466)
> at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.run(SmartImportJob.java:242)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22912:
------------------------------------------
Sorry for testing it so long. I had problems with proxy settings after testing CDK proxy availability.
[~snjeza] no, i have F24 installed at once.
I tested the patch, but combo box still has inappropriate size.
gtk3-3.20.9-1.fc24.x86_64
> Deploy Docker Wizard: Inappropriate project combo size
> ------------------------------------------------------
>
> Key: JBIDE-22912
> URL: https://issues.jboss.org/browse/JBIDE-22912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM1
>
> Attachments: deploy-to-docker-wizard-fc23.png, project_combo.png
>
>
> In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good.
> !project_combo.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík commented on JBDS-3981:
--------------------------------------
Nick, one more thing. I looked at rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm. It didn't work for me - same errors as yours. Then I looked at its content and one thing caught my eye: it contains org.mozilla.xulrunner.gtk.linux.x86_64. If it really has to (I'd be surprised) then there are architecture-specific binaries there and the resulting RPM should be *.x86_64.rpm, not *.noarch.rpm. It's not probably the main concern at this moment but is should be fixed.
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22969:
-------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.2.AM1
>
> Attachments: proxy_settings.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23015:
-------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Creating a route should have a default port
> -------------------------------------------
>
> Key: JBIDE-23015
> URL: https://issues.jboss.org/browse/JBIDE-23015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Fix For: 4.4.2.AM1
>
>
> When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail.
> There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others.
> The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation)
> To reproduce:
> - git clone https://github.com/redhat-helloworld-msa/aloha
> - mvn package
> - build docker image from Dockerfile, to CDK docker connection
> - deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23074) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Integration Tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23074?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-23074:
-------------------------------------
Assignee: Radim Hopp (was: Martin Malina)
[~rhopp], please create the 4.4.1.x branch and then close this JIRA. Thanks!
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Integration Tests]
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23074
> URL: https://issues.jboss.org/browse/JBIDE-23074
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Friendly Jira Robot
> Assignee: Radim Hopp
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [Integration Tests]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months