February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23891) EL syntax error: Expecting Expression on EL string concat operator

by thatsIch thatsIch (JIRA)

thatsIch thatsIch created JBIDE-23891: ----------------------------------------- Summary: EL syntax error: Expecting Expression on EL string concat operator Key: JBIDE-23891 URL: https://issues.jboss.org/browse/JBIDE-23891 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.4.2.Final Environment: Windows 10 Eclipse Neon.2 (4.6.2) JBoss Tools 4.4.2.Final (Marketplace) JavaEE 7 Reporter: thatsIch thatsIch Priority: Minor The EL 3.0 specification [1] states String Concatenation Operator - A += B To evaluate A += B ■ Coerce A and B to String. ■ Return the concatenated string of A and B. Used on a JSF Tag like {code:java} <h:outputText value="#{'foo' += 'bar'}" /> {code} leads to following warning: *EL syntax error: Expecting expression.* on the *=* part of the *+=* operator. [1] http://download.oracle.com/otn-pub/jcp/el-3_0-fr-eval-spec/EL3.0.FR.pdf -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23881) Properties: Builds are missing the cathegories and properties that exist in all other tab items

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23881?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23881. ------------------------------- Verifying this has been fixed along with JBIDE-23841. > Properties: Builds are missing the cathegories and properties that exist in all other tab items > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23881 > URL: https://issues.jboss.org/browse/JBIDE-23881 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, properties > Fix For: 4.4.3.Final > > Attachments: build-config-properties.png, build-properites.png > > > The "Builds" tab contains a list of builds that exist on the server. Selecting them unveil the properties of the selected build. > The same is valid for all other tabs like "Build Configs" , "Deployments", etc. But these other items all have cathegories like "Annotations", "Basic", "Labels", etc. > !build-config-properties.png! > "Builds" dont have these: > !build-properites.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23841) Properties view: "Details" tab wont tell you what kind of resource it's showing details for

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23841?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23841. ------------------------------- Verified in the latest 4.4.3 nightly. > Properties view: "Details" tab wont tell you what kind of resource it's showing details for > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23841 > URL: https://issues.jboss.org/browse/JBIDE-23841 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, properties > Fix For: 4.4.3.Final > > Attachments: properties-details-resource-type-missing.png > > > steps: > # ASSERT: make sure that you have an application in your OpenShift server > # EXEC: in OpenShift explorer: select your (application-) service and > # EXEC: open the Properties view and select the "Details" tab > # EXEC: try to figure out what kind of resource you are inspecting the details of > Result: > You have no indication for the kind of resource that is selected in the explorer > !properties-details-resource-type-missing.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23867) OCBinary: is mixing platform independent with dependent code

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23867?page=com.atlassian.jira.plugi... ] Jan Richter commented on JBIDE-23867: ------------------------------------- [~adietish] can you please close this one if you find the changes satisfactory? > OCBinary: is mixing platform independent with dependent code > ------------------------------------------------------------ > > Key: JBIDE-23867 > URL: https://issues.jboss.org/browse/JBIDE-23867 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > OCBinary is suing enums for the different platform. The platform instance is chosen right when you get the instance that you want to work with: > {code} > OCBinary#getInstance > {code} > {code} > public static OCBinary getInstance() { > if (SystemUtils.IS_OS_WINDOWS) { > return WINDOWS; > } else { > return OTHER; > } > } > {code} > But then, latter code (that was introduced later in #getSystemPathLocation ignoring it and start being platform independent again, even setting the default to be linux: > {code} > public String getSystemPathLocation() { > if (locationBinary == null) { > this.locationBinary = new CommandLocationBinary("oc"); > locationBinary.addPlatformLocation(Platform.OS_LINUX, OC_DEFAULTLOCATION_LINUX); > locationBinary.setDefaultPlatform(Platform.OS_LINUX); > } > return locationBinary.findLocation(); > } > {code} > Even worse is that the above code hard-codes the oc binary to be "oc" while the enum for windows is defining it as "oc.exe" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23822) Server adapter: is not working with oc v1.4.x

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23822?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23822. ------------------------------- Verified with 4.4.3 latest nightly. > Server adapter: is not working with oc v1.4.x > --------------------------------------------- > > Key: JBIDE-23822 > URL: https://issues.jboss.org/browse/JBIDE-23822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: Devstudio 10.3.0.AM2. > CDK 2.4 (OpenShift 3.4) > oc v1.4.1 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > > {noformat} > !ENTRY org.jboss.tools.openshift.core 2 0 2017-02-01 13:46:34.181 > !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy > !STACK 1 > org.eclipse.core.runtime.CoreException: Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:83) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Contains: OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist > !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181 > !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy > !SUBENTRY 2 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181 > !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist > !ENTRY org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219 > !MESSAGE Could not sync /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app > !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219 > !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23819) Preferences: Unable to determine oc 1.4.1 version

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23819?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23819. ------------------------------- Verified in the latest 4.4.3 nightly. > Preferences: Unable to determine oc 1.4.1 version > ------------------------------------------------- > > Key: JBIDE-23819 > URL: https://issues.jboss.org/browse/JBIDE-23819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: Devstudio 10.3.0.AM2, oc client v1.4.1 downloaded from https://github.com/openshift/origin/releases/tag/v1.4.1 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.3.Final > > Attachments: binary-not-oc.png, oc-14-not-recognized.png > > > Selecting oc version 1.4.1 [1] in OpenShift 3 preferences dialog results in "Could not determine your OpenShift client version". > [1] - https://github.com/openshift/origin/releases/tag/v1.4.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23788) Hibernate New and Noteworthy for 4.4.3.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23788?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23788. ------------------------------ Resolution: Done > Hibernate New and Noteworthy for 4.4.3.AM2 > --------------------------------------------------- > > Key: JBIDE-23788 > URL: https://issues.jboss.org/browse/JBIDE-23788 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-23786 #comment Create N&N for Hibernate 4.4.3.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4130) Environment variables are duplicated after several installations

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4130?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4130. ----------------------------- Verified in master and 1.3.0 latest build. > Environment variables are duplicated after several installations > ---------------------------------------------------------------- > > Key: JBDS-4130 > URL: https://issues.jboss.org/browse/JBDS-4130 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > Attachments: screenshot-1.png > > > Installer does not perform any checks at the moment before setting PATH environment variable. This issue affects only windows installer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4261) Create branding/design for APIs that are being pulled into DCP

by Ryszard Kozmik (JIRA)

[ https://issues.jboss.org/browse/JBDS-4261?page=com.atlassian.jira.plugin.... ] Ryszard Kozmik commented on JBDS-4261: -------------------------------------- Yes, here https://issues.jboss.org/browse/RHDENG-982 but this task doesn't belong in RHDENG. It's about frontend/design corrections of content on d.r.c site so it should be in DEVELOPER. > Create branding/design for APIs that are being pulled into DCP > -------------------------------------------------------------- > > Key: JBDS-4261 > URL: https://issues.jboss.org/browse/JBDS-4261 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: documentation > Reporter: Heinz Windzio > Fix For: LATER > > > Ryszard has now completed the back end work needed to connect the following docs to the DCP: > https://developers.redhat.com/apidocs/datagrid/7.0.0/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/modeshape/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/teiid/ > https://developers.redhat.com/apidocs/eap/7.0.0/ > You can see that it has the 'legacy' jboss styling at the top. I'm not sure if there is a consistent styling for the APIs that we need to adhere to, but logging this JIRA for someone to look into it and create it if needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4261) Create branding/design for APIs that are being pulled into DCP

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4261?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBDS-4261: ------------------------------------- [~unibrew] I think you are tracking this work in RHDENG. Is that right? > Create branding/design for APIs that are being pulled into DCP > -------------------------------------------------------------- > > Key: JBDS-4261 > URL: https://issues.jboss.org/browse/JBDS-4261 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: documentation > Reporter: Heinz Windzio > Fix For: LATER > > > Ryszard has now completed the back end work needed to connect the following docs to the DCP: > https://developers.redhat.com/apidocs/datagrid/7.0.0/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/modeshape/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/teiid/ > https://developers.redhat.com/apidocs/eap/7.0.0/ > You can see that it has the 'legacy' jboss styling at the top. I'm not sure if there is a consistent styling for the APIs that we need to adhere to, but logging this JIRA for someone to look into it and create it if needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017