December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21299) EL Knowledge Base Problem with PrimeFaces functions

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21299?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21299: ----------------------------------------------- Please try #{p:component('cc')}. Does it also have warning '"component" cannot be resolved'? I found that content assist in text {code} #{p: #{p:f} {code} after the first ':' does not work. However, it works for cases {code} #{p:c #{p:f} {code} and {code} #{p:} #{p:f} {code} Please try them. > EL Knowledge Base Problem with PrimeFaces functions > --------------------------------------------------- > > Key: JBIDE-21299 > URL: https://issues.jboss.org/browse/JBIDE-21299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x > Reporter: Andrei Ivanov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.x > > > The PrimeFaces functions are not recognized: > {noformat} > "ifAnyGranted" cannot be resolved > "ifGranted" cannot be resolved > "remoteUser" cannot be resolved > {noformat} > These are defined in {{org.primefaces.util.SecurityUtils}} and {{primefaces-5.3.jar/META-INF/primefaces-p.taglib.xml}}. > {code:xml} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > xmlns:p="http://primefaces.org/ui"> > #{p:ifAnyGranted('ROLE_USER, ROLE_ADMIN')} > #{p:ifGranted('ROLE_ADMIN')} > #{p:remoteUser()} > </html> > {code} > Similar to JBIDE-12317 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21313?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21313: -------------------------------- Labels: respin-a (was: ) > No web console URL for connection, project and resources > -------------------------------------------------------- > > Key: JBIDE-21313 > URL: https://issues.jboss.org/browse/JBIDE-21313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: respin-a > Fix For: 4.3.1.Beta1 > > Attachments: no_web_console_url.png > > > When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: > !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21313?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21313: -------------------------------- Fix Version/s: 4.3.1.Beta1 > No web console URL for connection, project and resources > -------------------------------------------------------- > > Key: JBIDE-21313 > URL: https://issues.jboss.org/browse/JBIDE-21313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: respin-a > Fix For: 4.3.1.Beta1 > > Attachments: no_web_console_url.png > > > When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: > !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21313?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21313: ----------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) > No web console URL for connection, project and resources > -------------------------------------------------------- > > Key: JBIDE-21313 > URL: https://issues.jboss.org/browse/JBIDE-21313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.3.1.Beta1 > > Attachments: no_web_console_url.png > > > When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: > !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20727) Docker explorer - Filters are confusing - options must be selected in order to be excluded

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20727?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20727. --------------------------------- OK, I am closing this. But [~ldimaggio] feel free to reopen if you disagree. > Docker explorer - Filters are confusing - options must be selected in order to be excluded > ------------------------------------------------------------------------------------------ > > Key: JBIDE-20727 > URL: https://issues.jboss.org/browse/JBIDE-20727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > The docker explorer filter requires the user to select which items to exclude, rather than include items. I think that it would be easier to follow if the filters were inclusive, not exclusive. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3552: --------------------------------- Fix Version/s: 9.1.0.Beta2 (was: 9.1.0.Beta1) > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21319) CDK start fails for no reason - it's actually running

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21319?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21319: --------------------------------------- Here's the console output: {code} Bringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 => 2222 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... default: No guest additions were detected on the base box for this VM! Guest default: additions are required for forwarded ports, shared folders, host only default: networking, and more. If SSH fails on this machine, please install default: the guest additions and repackage the box to continue. default: default: This is not an error message; everything may continue to work properly, default: in which case you may ignore this message. ==> default: Configuring and enabling network interfaces... ==> default: Registering box with vagrant-registration... ==> default: Rsyncing folder: /Users/rasp/git/openshift-vagrant/cdk-v2/ => /vagrant ==> default: Running provisioner: shell... default: Running: /var/folders/w_/sj0mnvys69q9mw41clt1yww00000gn/T/vagrant-shell20151214-7677-11ro0pq.sh ==> default: [INFO] Skipping Docker configuration. Already done. ==> default: Running provisioner: shell... default: Running: /var/folders/w_/sj0mnvys69q9mw41clt1yww00000gn/T/vagrant-shell20151214-7677-gxstcg.sh ==> default: [INFO] Skipping pull of OpenShift image ==> default: [INFO] Preparing OpenShift config ==> default: [INFO] Waiting for OpenShift config files to be created ==> default: [INFO] Configuring OpenShift via /var/lib/origin/openshift.local.config/master/master-config.yaml ==> default: [INFO] Starting OpenShift server ==> default: [INFO] Waiting for OpenShift sever to come up ... ==> default: [INFO] ... ==> default: Running provisioner: shell... default: Running: inline script ==> default: ==> default: You can now access OpenShift console on: https://10.1.2.2:8443/console ==> default: ==> default: To use OpenShift CLI, run: ==> default: $ vagrant ssh ==> default: $ oc status ==> default: ==> default: To become a cluster-admin, add '--config' to oc commands: ==> default: $ vagrant ssh ==> default: $ oc status --config=/var/lib/origin/openshift.local.config/master/admin.kubeconfig {code} So you can see that it started up just fine. So some problem with detection of the startup being completed? > CDK start fails for no reason - it's actually running > ----------------------------------------------------- > > Key: JBIDE-21319 > URL: https://issues.jboss.org/browse/JBIDE-21319 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2 > > > I just tried to start the CDK adapter. > After it all started, Eclipse showed me an error window saying: > {code} > Server cdk-v2 CDK Server failed to start. > {code} > The server views shows [Stopped], but running "vagrant status" in command line shows it's running. > I know this is not much information, but really I don't have anything else. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21319) CDK start fails for no reason - it's actually running

by Martin Malina (JIRA)

Martin Malina created JBIDE-21319: ------------------------------------- Summary: CDK start fails for no reason - it's actually running Key: JBIDE-21319 URL: https://issues.jboss.org/browse/JBIDE-21319 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.3.1.Beta2 I just tried to start the CDK adapter. After it all started, Eclipse showed me an error window saying: {code} Server cdk-v2 CDK Server failed to start. {code} The server views shows [Stopped], but running "vagrant status" in command line shows it's running. I know this is not much information, but really I don't have anything else. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21048) Download Runtimes should not require constantly typing credentials for each download

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21048?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21048. ------------------------------ Download runtimes now use credentials framework. Verified in JBDS 9.1.0.Beta1-v20151212-0638-B189. Closing. > Download Runtimes should not require constantly typing credentials for each download > ------------------------------------------------------------------------------------ > > Key: JBIDE-21048 > URL: https://issues.jboss.org/browse/JBIDE-21048 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: JBIDE-21048a.png, JBIDE-21048b.png > > > Download runtimes, when used for downloading EAP / JPP / Fuse runtimes, requires typing in credentials and verifying them. This can be made simpler for the user, either by persisting the credentials directly or by referencing the (possible) credentialing framework (JBIDE-21043) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20581) Wrong names used for servers added via runtime detection (WFLY10, EAP7)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20581?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-20581. ------------------------------ Verified in JBDS 9.1.0.Beta1-v20151212-0638-B189 > Wrong names used for servers added via runtime detection (WFLY10, EAP7) > ----------------------------------------------------------------------- > > Key: JBIDE-20581 > URL: https://issues.jboss.org/browse/JBIDE-20581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.CR1 > Environment: Nightly JBDS from 6.9.2015. > org.jboss.tools.runtime.core.feature (3.1.0.CR1-v20150905-0435-B808) > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > I tried to add WildFly 10 and EAP 7.0 servers via runtime detection and this is what i got: > * EAP 7.0 - Server name: "EAP 7.0" - shouldn't it be "JBoss EAP 7.0"? At least previous versions have "JBoss" in name ("JBoss EAP 6.4") > * WildFly 10 - Server name: "Wildfly 10.0". I think, that there should be capital F: "WildFly 10" > * WildFly 10 Servlet only distribution - Server name: "EAP-Web 10.0" - this seems completely wrong. > Btw. Does EAP 7 have servlet only distribution like WFLY9/10 has? I couldn't find any, but classes like `org.jboss.ide.eclipse.as.core.server.bean.ServerBeanTypeEAP70Web` suggest that there should be something somewhere ;-) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 December 2015