November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ] Cody Lerum updated JBIDE-21113: ------------------------------- Description: When adding a JSF phase listener to faces-config.xml {code} <lifecycle> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener> </lifecycle> {code} You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}} In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener. The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class was: When adding a JSF phase listener to faces-config.xml {code} <lifecycle> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener> </lifecycle> {code} You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}} In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html > Incorrect JSF Phase Listener Warning > ------------------------------------ > > Key: JBIDE-21113 > URL: https://issues.jboss.org/browse/JBIDE-21113 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Mars.1 > Java 8 > Reporter: Cody Lerum > > When adding a JSF phase listener to faces-config.xml > {code} > <lifecycle> > <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener> > </lifecycle> > {code} > You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}} > In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html > In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener. > The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21109) [application wizard] 2 connections from same server but for different users result in project mismatch

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21109?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21109. --------------------------------- Resolution: Done Labels: application_wizard upstream (was: application_wizard) Upstream fix has been applied. It fixes the problem in Eclipse. > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21109 > URL: https://issues.jboss.org/browse/JBIDE-21109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, upstream > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21109) [application wizard] 2 connections from same server but for different users result in project mismatch

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21109?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21109: ----------------------------------- Assignee: Fred Bricon > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21109 > URL: https://issues.jboss.org/browse/JBIDE-21109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21114) Dont stop watch client on disconnect

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21114: ------------------------------------- Summary: Dont stop watch client on disconnect Key: JBIDE-21114 URL: https://issues.jboss.org/browse/JBIDE-21114 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Jeff Cantrill Should just reconnect on error and leave watchclient running -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21114) Dont stop watch client on disconnect

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21114?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-21114: ------------------------------------- Assignee: Jeff Cantrill > Dont stop watch client on disconnect > ------------------------------------ > > Key: JBIDE-21114 > URL: https://issues.jboss.org/browse/JBIDE-21114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Should just reconnect on error and leave watchclient running -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-21113: ---------------------------------- Summary: Incorrect JSF Phase Listener Warning Key: JBIDE-21113 URL: https://issues.jboss.org/browse/JBIDE-21113 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsf Affects Versions: 4.3.0.Final Environment: Mars.1 Java 8 Reporter: Cody Lerum When adding a JSF phase listener to faces-config.xml {code} <lifecycle> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener> </lifecycle> {code} You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}} In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21030) Use newer Easymport (update Neon TP)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21030?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-21030. ------------------------------------ Resolution: Done > Use newer Easymport (update Neon TP) > ------------------------------------ > > Key: JBIDE-21030 > URL: https://issues.jboss.org/browse/JBIDE-21030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20... > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21072) Application wizard: Server templates tree is not rendered

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21072?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21072: --------------------------------------- {quote} I assume that the similarity is in the stacked panels being used in both cases (afaik the editor-pane is using a CTabFolder while we're using a TabFolder) which I assume use a native way to stack composites? {quote} All widgets in GTK3 are transparent, so that the "visible widget" term doesn't make sense. In my opinion that is the reason why a layout can be different depending on whether a component is visible or not. There are bugs similar to this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=465056, https://issues.jboss.org/browse/JBIDE-16503 ... > Application wizard: Server templates tree is not rendered > --------------------------------------------------------- > > Key: JBIDE-21072 > URL: https://issues.jboss.org/browse/JBIDE-21072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3, upstream > Fix For: 4.3.1.Beta1 > > Attachments: wizard.png > > > When I select at first a local template then proceed to next wizard page in a New OpenShift Application wizard and hit back button then tree containing server templates is not rendered correctly. Only search text field is shown but the tree with templates is missing there. > !wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21003: ------------------------------------ Merged in 4.60.x: https://github.com/jbosstools/jbosstools-target-platforms/commit/7456789a... Now I need to do the same for the 4.50.x and 4.51.x branches. > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: p2diff.jbdevstudio_v3.txt > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21106) Update to m2e 1.7 and m2e-wtp 1.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21106?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21106: ------------------------------------ My PR applied in 4.60.x branch. Building 4.60.0.Alpha1-SNAPSHOT: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >=472 > Update to m2e 1.7 and m2e-wtp 1.3 > --------------------------------- > > Key: JBIDE-21106 > URL: https://issues.jboss.org/browse/JBIDE-21106 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > As announced a week ago [1], m2e 1.7 is available. > [1] http://lists.jboss.org/pipermail/jbosstools-dev/2015-November/010757.html > So, I suppose we should updated the JBT 4.4 and JBDS 10.0 target platforms to include this new version. > Luckily, the m2e bits are already in Neon M3 so no new mirror is needed; but I need to know if there are any other m2e-* pieces which ALSO need to be updated in lock-step at the same time. > https://github.com/jbosstools/jbosstools-target-platforms/blob/4.60.x/jbd... > https://github.com/jbosstools/jbosstools-target-platforms/blob/4.60.x/jbo... > Please clarify which m2e-* projects also need updating, or if in fact we ONLY want to include m2e 1.7 instead of 1.62, and change none of the rest of the m2e family. > Also, if this change should be backported to the Mars-based target platforms for JBT 4.3.x / JBDS 9.x, let me know that too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015