June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26075) Support FacesContext Injection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26075?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26075: ---------------------------------- Assignee: Jeff MAURY > Support FacesContext Injection > ------------------------------ > > Key: JBIDE-26075 > URL: https://issues.jboss.org/browse/JBIDE-26075 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, jsf > Affects Versions: 4.5.3.Final > Environment: JSF 2.3 > Reporter: Cody Lerum > Assignee: Jeff MAURY > Fix For: 4.6.0.Final > > > JSF 2.3 now produces various beans for CDI > https://arjan-tijms.omnifaces.org/p/jsf-23.html#1316 > However currently the following gives a > No bean is eligible for injection to the injection point [JSR-365 §5.2.2] > {code} > @Inject > private FacesContext facesContext; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26075) Support FacesContext Injection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26075?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26075: ------------------------------- Fix Version/s: 4.6.0.Final > Support FacesContext Injection > ------------------------------ > > Key: JBIDE-26075 > URL: https://issues.jboss.org/browse/JBIDE-26075 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, jsf > Affects Versions: 4.5.3.Final > Environment: JSF 2.3 > Reporter: Cody Lerum > Assignee: Jeff MAURY > Fix For: 4.6.0.Final > > > JSF 2.3 now produces various beans for CDI > https://arjan-tijms.omnifaces.org/p/jsf-23.html#1316 > However currently the following gives a > No bean is eligible for injection to the injection point [JSR-365 §5.2.2] > {code} > @Inject > private FacesContext facesContext; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26075) Support FacesContext Injection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26075?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26075: ------------------------------- Sprint: devex #151 June 2018 > Support FacesContext Injection > ------------------------------ > > Key: JBIDE-26075 > URL: https://issues.jboss.org/browse/JBIDE-26075 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, jsf > Affects Versions: 4.5.3.Final > Environment: JSF 2.3 > Reporter: Cody Lerum > Assignee: Jeff MAURY > Fix For: 4.6.0.Final > > > JSF 2.3 now produces various beans for CDI > https://arjan-tijms.omnifaces.org/p/jsf-23.html#1316 > However currently the following gives a > No bean is eligible for injection to the injection point [JSR-365 §5.2.2] > {code} > @Inject > private FacesContext facesContext; > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25446. --------------------------------- > Windows/Mac slave gets disconnected during job execution > -------------------------------------------------------- > > Key: JBIDE-25446 > URL: https://issues.jboss.org/browse/JBIDE-25446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Blocker > Labels: jenkins > Fix For: 4.6.0.AM2 > > > During jenkins job execution slaves is disconnected with exception > {code} > 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available.... > 19:09:32 FATAL: command execution failed > 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected. > 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191) > 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) > 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035) > 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399) > 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367) > 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) > 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205) > 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) > 19:09:32 at hudson.model.Run.execute(Run.java:1728) > 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) > 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98) > 19:09:32 at hudson.model.Executor.run(Executor.java:404) > 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148] > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635) > 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 19:09:32 at java.lang.Thread.run(Thread.java:748) > 19:09:32 Caused by: java.io.IOException: Connection reset by peer > 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197) > 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564) > 19:09:32 ... 6 more > 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4704) Red Hat JBoss Developer Studio marketplace entry info contains irrelevant/outdated information

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4704?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-4704. ------------------------------- > Red Hat JBoss Developer Studio marketplace entry info contains irrelevant/outdated information > ---------------------------------------------------------------------------------------------- > > Key: JBDS-4704 > URL: https://issues.jboss.org/browse/JBDS-4704 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: marketplace > Affects Versions: 11.3.0.GA > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Fix For: 11.3.0.GA > > > Marketplace entry https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio/ contains: > ??Single Development Tool, Tailored for Extreme Productivity. JBoss® Developer Studio provides superior support for your entire development lifecycle. It includes a broad set of tooling capabilities and support for multiple programming models and frameworks, including Java™ Enterprise Edition 6, RichFaces, JavaServer Faces (JSF), Enterprise JavaBeans (EJB), Java Persistence API (JPA), and Hibernate®, JAX-RS with RESTEasy, OpenShift, Apache Camel, Red Hat JBoss Fuse, Contexts Dependency Injection (CDI), HTML5, and many other popular technologies. It provides developer choice in supporting multiple JVMs, productivity with Maven, and in testing with Arquillian. It is fully tested and certified to ensure that all its plug-ins, runtime components, and their dependencies are compatible with each other.?? > There are old stuff like Java EE 6, RichFaces (aren't those quite outdated?) and at the end there is information about arquillian, which is removed as well. > Please, update according to link here: https://developers.redhat.com/products/devstudio/overview/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26036) Update bundled minishift.yaml file in resources folder to correspond with stack version

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26036?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26036: ---------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.0.AM3) > Update bundled minishift.yaml file in resources folder to correspond with stack version > --------------------------------------------------------------------------------------- > > Key: JBIDE-26036 > URL: https://issues.jboss.org/browse/JBIDE-26036 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.6.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.0.Final > > > Edit minishift.yaml file that resides in jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/resources to have corresponding content as jboss-stack/minishift.yaml file. We want to have the same content available when something fails to read stack's yaml file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26020) Find cause of CDI 1.0 and 1.1 itests instability

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26020?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26020: ---------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.0.AM3) > Find cause of CDI 1.0 and 1.1 itests instability > ------------------------------------------------ > > Key: JBIDE-26020 > URL: https://issues.jboss.org/browse/JBIDE-26020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, integration-tests > Affects Versions: 4.6.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.6.0.Final > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... and https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... shows that there are some dirty editor states, etc. Review tests and find errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25921) MacOS machines with label mac_xhyve are not capable of running cdk.itests

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25921?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25921: ---------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.0.AM3) > MacOS machines with label mac_xhyve are not capable of running cdk.itests > ------------------------------------------------------------------------- > > Key: JBIDE-25921 > URL: https://issues.jboss.org/browse/JBIDE-25921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, qa > Affects Versions: 4.5.3.Final > Environment: Mac OS High Sierra > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.6.0.Final > > > Recently, cdk.itests are not able to be run on Mac OS machines within jenkins with label mac_xhyve. > * find out cause of instability > * add another mac os machines into label (dev_platform_mac) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4708) Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4708?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4708: ---------------------------------- Still occurring in AM3 stage bits. Problem could be o.sonatype.m2e.egit.feature requiring egit 4.11, but 5.0 is in photon. Best option could be to disable the m2e.egit feature from central/devstudio. > Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently > --------------------------------------------------------------------------- > > Key: JBDS-4708 > URL: https://issues.jboss.org/browse/JBDS-4708 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.0.0.AM3 > > Attachments: remediation-1.png, remediation-2.png, remediation-jbt-central.png > > > Problem appears to be a hard upper limit from org.sonatype.m2e.egit 0.15.0.20161027 on egit.core [3.0.0,5.0.0). > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > Software currently installed: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > Only one of the following can be installed at once: > Git integration for Eclipse - Core 4.11.0.201803080745-r (org.eclipse.egit.core 4.11.0.201803080745-r) > Git integration for Eclipse - Core 5.0.0.201805151920-m7 (org.eclipse.egit.core 5.0.0.201805151920-m7) > Git integration for Eclipse - Core 4.10.0.201712302008-r (org.eclipse.egit.core 4.10.0.201712302008-r) > Git integration for Eclipse - Core 5.0.0.201805221745-rc1 (org.eclipse.egit.core 5.0.0.201805221745-rc1) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > To: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpmdeps.feature.feature.group [12.0.0.v20180418-2342,12.0.0.v20180418-2342] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 12.0.0.v20180418-2342 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 12.0.0.v20180418-2342) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit.feature.feature.group 0.0.0 > Cannot satisfy dependency: > From: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > To: org.eclipse.equinox.p2.iu; org.eclipse.egit.core [5.0.0.201805151920-m7,5.0.0.201805151920-m7] > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit 0.15.0.201610271523) > To: osgi.bundle; org.eclipse.egit.core [3.0.0,5.0.0) > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit.feature.feature.group 0.15.0.201610271523) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit [0.15.0.201610271523,0.15.0.201610271523]{code} > As such we can either: > * install devstudio (which requires m2e.egit) and uninstall egit and egit.mylyn features to do so, or > !remediation-2.png|thumbnail! > * upgrade to egit 5.0.0.20180522 (rc1) and not be able to install devstudio 12.0.0.AM2. > !remediation-1.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text

by Richard Fontana (JIRA)

[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ] Richard Fontana commented on JBDS-4706: --------------------------------------- [~rpdavis] What is the issue with the EULA - the fact that it refers to "JBoss" at all? From the above I understand that we are still referring to "Red Hat JBoss Middleware". If we are actually expunging all use of "JBoss" from the middleware products, I suppose the EULA should be updated to reflect that, though it is not a very important thing. Erika Nelson is the right contact for that. > Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text > --------------------------------------------------------------------------------------------- > > Key: JBDS-4706 > URL: https://issues.jboss.org/browse/JBDS-4706 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.0.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.0.0.AM3 > > Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico > > > Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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