May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21857: ------------------------------------- Thanks for the help, Thomas. I'll try to ping someone else. > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24525) Create and use Oxygen.0.RC4 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24525?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24525: ------------------------------- Description: Once available on Jun 16/2017, we should create a new 4.70.0.AM2-SNAPSHOT target platform containing Oxygen.0.RC4 bits. https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... Story points: 21 (fibonacci) jbt tp, jbds tp, central tp; jbt-build-sites, jbds site build; update install/matrix jobs to use new Eclipse JEE/platform binary; mailing list announcements was: Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... Story points: 21 (fibonacci) jbt tp, jbds tp, central tp; jbt-build-sites, jbds site build; update install/matrix jobs to use new Eclipse JEE/platform binary; mailing list announcements > Create and use Oxygen.0.RC4 target platform > ------------------------------------------- > > Key: JBIDE-24525 > URL: https://issues.jboss.org/browse/JBIDE-24525 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM2 > > > Once available on Jun 16/2017, we should create a new 4.70.0.AM2-SNAPSHOT target platform containing Oxygen.0.RC4 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24525) Create and use Oxygen.0.RC4 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24525?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24525: ------------------------------- Affects Version/s: 4.5.0.AM2 (was: 4.4.1.AM1) > Create and use Oxygen.0.RC4 target platform > ------------------------------------------- > > Key: JBIDE-24525 > URL: https://issues.jboss.org/browse/JBIDE-24525 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM2 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24525) Create and use Oxygen.0.RC4 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24525?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24525: ------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/252, https://github.com/jbosstools/jbosstools-discovery/pull/342, https://github.com/jbosstools/jbosstools-target-platforms/pull/258, https://github.com/jbosstools/jbosstools-discovery/pull/356) > Create and use Oxygen.0.RC4 target platform > ------------------------------------------- > > Key: JBIDE-24525 > URL: https://issues.jboss.org/browse/JBIDE-24525 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM2 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24525) Create and use Oxygen.0.RC4 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24525?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24525: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Create and use Oxygen.0.RC4 target platform > ------------------------------------------- > > Key: JBIDE-24525 > URL: https://issues.jboss.org/browse/JBIDE-24525 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM2 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4421) DevSuite 1.4 Mac Oops something went wrong (devstudio download timeout)

by Robert Terzi (JIRA)

Robert Terzi created JBDS-4421: ---------------------------------- Summary: DevSuite 1.4 Mac Oops something went wrong (devstudio download timeout) Key: JBDS-4421 URL: https://issues.jboss.org/browse/JBDS-4421 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: installer Environment: DevStudio 1.4 installer, Mac OS X 10.10.5 Reporter: Robert Terzi The installer gives the error "Oops Something went wrong". The problem seems to be the DevStudio download is timing out. There is an ESOCKETTIMEOUT error in the log. Seems like anytime the download pauses for 5 seconds it times out. If there is a 5 second timeout that is probably too small outside of the red hat network. Note I downloaded DevStudio several times successfully on windows. The cdk/minishift download succeeds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24525) Create and use Oxygen.0.RC4 target platform

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24525: ---------------------------------- Summary: Create and use Oxygen.0.RC4 target platform Key: JBIDE-24525 URL: https://issues.jboss.org/browse/JBIDE-24525 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: target-platform Affects Versions: 4.4.1.AM1 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 4.5.0.AM1 Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... Story points: 21 (fibonacci) jbt tp, jbds tp, central tp; jbt-build-sites, jbds site build; update install/matrix jobs to use new Eclipse JEE/platform binary; mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24484) deprecate jbosstools projects / move to Central ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24484?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24484: ------------------------------------ Moving to Central and out of the Marketplace / CoreTools "Abridged JBoss Tools" category makes these "deprecated" projects slightly harder to use & install. It also implies less support as they're no longer part of the MAIN JBoss Tools / devstudio release, but rather are extras users COULD choose to install at their own risk. So it's kind of a marketing thing - downgrading these projects from Core to Optional. > deprecate jbosstools projects / move to Central ? > ------------------------------------------------- > > Key: JBIDE-24484 > URL: https://issues.jboss.org/browse/JBIDE-24484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > With the upcoming plan for devstudio 11 / jbosstools 4.5, it may be time to consider moving parts of jbosstools / devstudio out of the Core Tools category and into Central as optional installs. Then in future we can deprecate them / remove them. > Here's the list of projects in jbosstools: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_proje... > https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j... > Once we have an idea of which projects could be moved/removed/deprecated, we can open subtasks for those projects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24484) deprecate jbosstools projects / move to Central ?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24484?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-24484: ---------------------------------------- It makes sense to stop building unchanged components. But why moving them to Central? > deprecate jbosstools projects / move to Central ? > ------------------------------------------------- > > Key: JBIDE-24484 > URL: https://issues.jboss.org/browse/JBIDE-24484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > With the upcoming plan for devstudio 11 / jbosstools 4.5, it may be time to consider moving parts of jbosstools / devstudio out of the Core Tools category and into Central as optional installs. Then in future we can deprecate them / remove them. > Here's the list of projects in jbosstools: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_proje... > https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j... > Once we have an idea of which projects could be moved/removed/deprecated, we can open subtasks for those projects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24184: ------------------------------------------ this caused more work than initially estimated. Postponing to 4.5.0.AM2 > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2017