April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21606: ------------------------------------- I'm a bit confused here. I checked out the html5 project from central and the pom.xml has the following: {code} <maven.compiler.target>1.6</maven.compiler.target> <version.jboss.maven.plugin>7.4.Final</version.jboss.maven.plugin> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <version.surefire.plugin>2.10</version.surefire.plugin> <version.org.eclipse.m2e>1.0.0</version.org.eclipse.m2e> <maven.compiler.source>1.6</maven.compiler.source> {code} So it seems it should be compiling with a class version of "50", which should be deployable on an eap using java6. [~mmalina] Can you help track down why it's behaving this way for you? > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21606: ------------------------------------- What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server. eg: - module compiled with Java 7, EAP 6.x running with Java 6 : Error - module compiled with Java 7, EAP 6.x running with Java 7+ : No problem > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21606 at 4/27/16 6:46 PM: -------------------------------------------------------------- What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server. eg: - module compiled with Java 7, EAP 6.x running with Java 6 : Error - module compiled with Java 7, EAP 6.x running with Java 7+ : No problem That really sound like an upstream problem was (Author: fbricon): What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server. eg: - module compiled with Java 7, EAP 6.x running with Java 6 : Error - module compiled with Java 7, EAP 6.x running with Java 7+ : No problem > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21606 at 4/27/16 6:46 PM: -------------------------------------------------------------- What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server. eg: - module compiled with Java 7, EAP 6.x running with Java 6 : Error - module compiled with Java 7, EAP 6.x running with Java 7+ : No problem That really sounds like an upstream problem was (Author: fbricon): What is actually needed here is a validation mechanism that detects the server module' compilation level matches the Server's actual JDK, regardless of the minimum Facet supported by said server. eg: - module compiled with Java 7, EAP 6.x running with Java 6 : Error - module compiled with Java 7, EAP 6.x running with Java 7+ : No problem That really sound like an upstream problem > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21606: ------------------------------------- Unsupported version: 51.0 means it was compiled by java7 and running on java6. So java8 isn't the issue. > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22224) Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22224?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-22224. --------------------------------- Resolution: Done Included in JBIDE-22174 > Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22224 > URL: https://issues.jboss.org/browse/JBIDE-22224 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3, ux > Fix For: 4.4.0.Alpha1 > > > When I am trying to deploy a docker image via context menu of a docker image in Docker Explorer, I am prompted every time to confirm Connection dialog, although I have an established connection in OpenShift Explorer view. It's pretty annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22224) Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22224?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22224: -------------------------------- Issue Type: Enhancement (was: Bug) Story Points: 1 > Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22224 > URL: https://issues.jboss.org/browse/JBIDE-22224 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3, ux > Fix For: 4.4.0.Alpha1 > > > When I am trying to deploy a docker image via context menu of a docker image in Docker Explorer, I am prompted every time to confirm Connection dialog, although I have an established connection in OpenShift Explorer view. It's pretty annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21422) Server adapter editor: details should be editable

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21422?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21422: -------------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > Server adapter editor: details should be editable > ------------------------------------------------- > > Key: JBIDE-21422 > URL: https://issues.jboss.org/browse/JBIDE-21422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Currently when I open a server adapter overview (by double click on a server adapter) there is whole section of details to which project it is bind to, paths etc. in the Project Settings section. This area is not editable. It would be nice to allow user modify this, to allow to choose different eclipse project or fix path if it was filled in wrong... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22174?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22174: -------------------------------- Story Points: 8 > Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22174 > URL: https://issues.jboss.org/browse/JBIDE-22174 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3866: ----------------------------------- [~rob.stryker] can you please take a look? > vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server > ---------------------------------------------------------------------------------------- > > Key: JBDS-3866 > URL: https://issues.jboss.org/browse/JBDS-3866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (previous installs of CDK and dependencies) > Reporter: Robert Terzi > Fix For: 10.x > > > vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. > The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. > The CDK server was shown as 'Started, Sychronized'. > The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. > Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016