[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21857:
---------------------------------------
Few observations. After starting debugging JMX is still disconnected, probably this should get fixed. After restarting a module, when a noncompatible HCR change is done, debugger still say it is out of sync, even though module has been redeployed on a remote server.
> 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.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> 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)
9 years, 4 months
[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-4095.
-------------------------------
I never had this problem and without Nick's workspace, it's kind of hard to replicate - I guess I could alter my existing log, but I'm not sure where exactly to put this date.
I checked the commit and it seems alright.
Closing. Please let us know if this issue reappears.
> unparseable date in o.j.t.foundation.checkup
> --------------------------------------------
>
> Key: JBDS-4095
> URL: https://issues.jboss.org/browse/JBDS-4095
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: foundation
> Affects Versions: 10.2.0.AM1
> Environment: {code}
> Red Hat JBoss Developer Studio
> Version: 10.2.0.AM1
> Build id: AM1-v20160923-1714-B6096
> Build date: 20160923-1714
> $➔ uname -a
> Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1
> $➔ java -version
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 10.2.0.AM2
>
> Attachments: unparesable-date.png
>
>
> Just started up devstudio 10.2.0.AM1-v20160923-1714-B6096 and got this error:
> {code}
> Unparseable date: "Thu Oct 06 13:55:38 EDT 2016"
> java.text.ParseException: Unparseable date: "Thu Oct 06 13:55:38 EDT 2016"
> at java.text.DateFormat.parse(DateFormat.java:366)
> at org.jboss.tools.foundation.checkup.JVMProblemDetector.getSessionDate(JVMProblemDetector.java:677)
> at org.jboss.tools.foundation.checkup.JVMProblemDetector.scanLine(JVMProblemDetector.java:240)
> at org.jboss.tools.foundation.checkup.JVMProblemDetector.readLogFile(JVMProblemDetector.java:186)
> at org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:118)
> at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:77)
> at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:53)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2829)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-3973) DevSuite Installer for MAC OS X
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3973?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3973:
--------------------------------
Description:
DevSuite should provide installer for Mac OS X and match features available under Windows:
1. Online and bundle installer distributions;
2. Detection of installed software;
3. Optional installation for any component from software stack;
4. Installation for vagrant and virtualbox from apple disk image (.dmg files);
5. Starting DevStudio from installer's last page;
6. Adding installed components to PATH.
was:
DevSuite should provide installer for Mac OS X and that leads to several problems to solve:
1. Install Software out of [Apple Disk Image|https://en.wikipedia.org/wiki/Apple_Disk_Image];
2. Download and install Java VM if it is not present or version is less than required;
3. Create Apple Disk Image for installer itself.
> DevSuite Installer for MAC OS X
> -------------------------------
>
> Key: JBDS-3973
> URL: https://issues.jboss.org/browse/JBDS-3973
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.x
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.GA
>
>
> DevSuite should provide installer for Mac OS X and match features available under Windows:
> 1. Online and bundle installer distributions;
> 2. Detection of installed software;
> 3. Optional installation for any component from software stack;
> 4. Installation for vagrant and virtualbox from apple disk image (.dmg files);
> 5. Starting DevStudio from installer's last page;
> 6. Adding installed components to PATH.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4047) Uninstaller does not clean up Path
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4047?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4047:
--------------------------------
Labels: new_and_noteworthy (was: )
> Uninstaller does not clean up Path
> ----------------------------------
>
> Key: JBDS-4047
> URL: https://issues.jboss.org/browse/JBDS-4047
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 10.2.0.AM2
>
>
> After running the uninstall script all the PATH entries pointing to the devsuite install folder remain untouched. My guess is the actual folder these entries are compared to is not the root install folder, but the uninstall one.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4047) Uninstaller does not clean up Path
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4047?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-4047.
-------------------------------
Resolution: Done
> Uninstaller does not clean up Path
> ----------------------------------
>
> Key: JBDS-4047
> URL: https://issues.jboss.org/browse/JBDS-4047
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 10.2.0.AM2
>
>
> After running the uninstall script all the PATH entries pointing to the devsuite install folder remain untouched. My guess is the actual folder these entries are compared to is not the root install folder, but the uninstall one.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months