July 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 resolved JBIDE-21606. --------------------------------- Resolution: Partially Completed > 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.1.AM2 > > > 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, 9 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: ------------------------------------- After reviewing the redhat access document, it's clear that creating a separate runtime type for eap6.4 is unfeasible. The common intended JRE for EAP 6.1+ is basically java7. All are guarenteed to work for java7, so I'll bump the default for all EAP 6.1+ to use java7 by default. But making java 8 the default for these types is simply not feasible because the default execution environment is set before the user gets a chance to set the runtime home directory. So we really have no ability to figure this out in advance. On the other hand, once the user types in a home directory, I think it'd be a bit jarring if we started changing the selected execution environment based on what was typed in the runtime home directory field. So... I'm closing this as partially complete. It's not the best result but it's what we can do. > 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.1.AM2 > > > 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, 9 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 updated JBIDE-21606: -------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.x) > 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.1.AM2 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-662) Add edited Advanced Install Task instructions to related docs

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-662?page=com.atlassian.jira.plug... ] Misha Ali edited comment on TOOLSDOC-662 at 7/5/16 12:59 AM: ------------------------------------------------------------- [~supriya.bharadwaj] please follow up on this. Is it even required? If not, lets close off this issue. I suspect Alexey is the one to talk to about permissions now rather than Max. was (Author: mhusnain): [~supriya.bharadwaj] please follow up on this. Is it even required? If not, lets close off this issue. > Add edited Advanced Install Task instructions to related docs > ------------------------------------------------------------- > > Key: TOOLSDOC-662 > URL: https://issues.jboss.org/browse/TOOLSDOC-662 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Add edited Advanced Install Task instructions to following related docs: > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/cu... > 2. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-662) Add edited Advanced Install Task instructions to related docs

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-662?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-662: ------------------------------------ [~supriya.bharadwaj] please follow up on this. Is it even required? If not, lets close off this issue. > Add edited Advanced Install Task instructions to related docs > ------------------------------------------------------------- > > Key: TOOLSDOC-662 > URL: https://issues.jboss.org/browse/TOOLSDOC-662 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Add edited Advanced Install Task instructions to following related docs: > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/cu... > 2. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-700) JBDS 9.1 Beta2: Additional docker functionality

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-700?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-700. ------------------------------ Resolution: Duplicate > JBDS 9.1 Beta2: Additional docker functionality > ----------------------------------------------- > > Key: TOOLSDOC-700 > URL: https://issues.jboss.org/browse/TOOLSDOC-700 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Docker > > Docker (in 9.0.0, adding CDK target and usability improvements): > - [Server Adapter to start/stop/restart/auto-configure the CDK's Vagrant VM|https://issues.jboss.org/browse/JBIDE-20153] > - docker run > - docker build > - docker logs > - run/build as launch configurations so users can rerun -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-742) JBDS 9.0 CDK Documentation Fixes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-742?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-742. ------------------------------ Resolution: Incomplete Description > JBDS 9.0 CDK Documentation Fixes > -------------------------------- > > Key: TOOLSDOC-742 > URL: https://issues.jboss.org/browse/TOOLSDOC-742 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17181: ------------------------------------- [~mmalina] Is this still replicatable?? > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-17181: ----------------------------------- Assignee: Martin Malina (was: Rob Stryker) > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.AM2 > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17181: -------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.2.x) > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.AM2 > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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