[JBoss JIRA] (JBIDE-21115) Dont stop watch client on disconnect
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21115:
----------------------------------------
Summary: Dont stop watch client on disconnect
Key: JBIDE-21115
URL: https://issues.jboss.org/browse/JBIDE-21115
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Fix For: 4.4.0.Alpha1
Should just reconnect on error and leave watchclient running
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21113:
-----------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
(was: 4.3.x)
(was: 4.4.x)
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21113
> URL: https://issues.jboss.org/browse/JBIDE-21113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> 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
[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21113:
--------------------------------------
Assignee: Viacheslav Kabanovich
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21113
> URL: https://issues.jboss.org/browse/JBIDE-21113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.x, 4.4.x
>
>
> 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
[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21113:
-----------------------------------
Fix Version/s: 4.3.x
4.4.x
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21113
> URL: https://issues.jboss.org/browse/JBIDE-21113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Fix For: 4.3.x, 4.4.x
>
>
> 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
[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21113:
-----------------------------------
Issue Type: Bug (was: Feature Request)
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21113
> URL: https://issues.jboss.org/browse/JBIDE-21113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> 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
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21105:
----------------------------------------
org.jboss.tools.birt has not been changed for ages (besides plugins versions updates, etc.). We do not have any automated tests there. Does QE test it manually or using any integration automated tests? [~ldimaggio]?
If org.eclipse.birt (in neon) depends on jetty [9.2, 10) then I would suggest:
1. Update our TP to whatever jetty 9.3.* we need (and what is included in neon) for livereload, browsersim, etc.
2. Remove other jetty's from our TP.
3. Update birt to the latest version in our TP. Keep an eye on it and update when needed before GA release.
4. Deprecate org.jboss.tools.birt in JBT 4.4.0.
5. Remove eclipse.birt and jboss.tools.birt from JBT 4.5
If we still want to support Birt then we skip #4 and #5.
[~maxandersen] WDYT?
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20764:
------------------------------------------
In https://issues.jboss.org/browse/CLOUD-243?focusedCommentId=13124018&page=... a label *org.jboss.deployments-dir* on the image was added for eap images. The equivalent for non-eap images isnt provided yet, though and still needs to be done. As discussed with [~kconner] the label will thus change to something non-eap specific and provided across openshift images (as suggested by [~maxandersen] in https://issues.jboss.org/browse/CLOUD-243?focusedCommentId=13130164&page=...)
> Create Server Adapter for OpenShift 3 applications
> --------------------------------------------------
>
> Key: JBIDE-20764
> URL: https://issues.jboss.org/browse/JBIDE-20764
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: new_and_noteworthy, openshift_v3
> Fix For: 4.3.1.Beta1
>
> Attachments: server adapter wizard.bmml, server adapter wizard.png
>
>
> get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed.
> Server status= matching deployment pod status
> Possible menus:
> - Start/Stop
> - Show Web Console
> - Port Forwarding
> - Stream logs
> [~maxandersen] can you think of anything else?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months