July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4461: ---------------------------------- The owner is you, Jeff. See RTD deck slide 25, with comments and assignments on the right hand side: https://docs.google.com/presentation/d/19v5HMRma0NVn2QD47-n6TmjvrO1YfXUyY... > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4461: ----------------------------- Attachment: (was: firstbase.png) > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4461: ----------------------------- Attachment: (was: whosonfirst.png) > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4461: ----------------------------- Attachment: (was: whatsonsecond.png) > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4461: ----------------------------- Attachment: firstbase.png whatsonsecond.png whosonfirst.png > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24657) CDI 1.1 and above should ignore static and private final methods when checking for unproxyable beans

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24657?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24657: ---------------------------------- Assignee: Jeff MAURY > CDI 1.1 and above should ignore static and private final methods when checking for unproxyable beans > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-24657 > URL: https://issues.jboss.org/browse/JBIDE-24657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Dos Moonen > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > > CDI 1.0 prohibits "classes which are declared final or have final methods" being normal scoped beans. > CDI 1.1 relaxes it to "classes which have non-static, final methods with public, protected or default visibility" > JBoss Tools adds a warning for all finals methods, regardless of the project's CDI version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24657) CDI 1.1 and above should ignore static and private final methods when checking for unproxyable beans

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24657?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24657: ------------------------------- Fix Version/s: 4.5.0.Final > CDI 1.1 and above should ignore static and private final methods when checking for unproxyable beans > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-24657 > URL: https://issues.jboss.org/browse/JBIDE-24657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Dos Moonen > Assignee: Jeff MAURY > Fix For: 4.5.0.Final > > > CDI 1.0 prohibits "classes which are declared final or have final methods" being normal scoped beans. > CDI 1.1 relaxes it to "classes which have non-static, final methods with public, protected or default visibility" > JBoss Tools adds a warning for all finals methods, regardless of the project's CDI version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24145) Command to tune memory requirements for a deployment

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24145?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24145: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM2) > Command to tune memory requirements for a deployment > ---------------------------------------------------- > > Key: JBIDE-24145 > URL: https://issues.jboss.org/browse/JBIDE-24145 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23869: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.5.0.Final > > Attachments: failure.png, image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24682: ---------------------------------- Description: Due to changes in upstream project the 'minishift version' command returns different lines. CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: {code} Minishift version: 1.0.0+4f8cb6d CDK Version: 3.0.0-2 {code} vs. CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: {code} minishift v1.2.0+001371f CDK Version:3.0.0-13072017-1 {code} And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... was: Due to changes in upstream project the 'minishift version' command returns different lines. CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: {code} Minishift version: 1.0.0+4f8cb6d CDK Version: 3.0.0-2 {code} vs. CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: {code} minishift v1.2.0+001371f CDK Version:3.0.0-13072017-1 {code} And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version". Please, change the VERSION_KEY at [CDK3ServerWizardFragment|CDK3ServerWizardFragment] from "Minishift Version" -> "minishift". We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. I do not know if we plan to do so, it is just an idea... > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 2017