[JBoss JIRA] (JBDS-4087) Mark as invalid Vagrant versions known to be not working
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4087?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4087:
--------------------------------
Sprint: devex #122 October 2016
> Mark as invalid Vagrant versions known to be not working
> --------------------------------------------------------
>
> Key: JBDS-4087
> URL: https://issues.jboss.org/browse/JBDS-4087
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> Vagrant version superior to 1.8.4 are known to be non-working, please mark them as invalid during installation of the components isntead of saying that there is a newer version.
> For my part there was no clue on what was the issue, i was based on the latest at the moment 1.8.6.
> When using JBDS, I had a timeout when trying to launch the Container in Server view and the console starting the server was displaying no errors
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ]
Rob Stryker updated JBDS-4095:
------------------------------
Sprint: devex #121 October 2016 (was: devex #122 October 2016)
> 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
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4095 at 10/13/16 9:18 PM:
------------------------------------------------------------
We can use p2.inf to add things into eclipse.ini.
Which plugin's install process should add a flag? (We can also remove a flag on uninstall.)
For example...
https://github.com/ferstl/eclipse-ini/blob/master/p2.inf
was (Author: nickboldt):
We can use p2.inf to add things into eclipse.ini.
Which plugin's install process should add a flag? (We can also remove a flag on uninstall.)
> 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
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4095:
----------------------------------
We can use p2.inf to add things into eclipse.ini.
Which plugin's install process should add a flag? (We can also remove a flag on uninstall.)
> 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
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-4095:
-----------------------------------
It was thought we could find a way to not read logs and make this less error prone. tl;dr: there isn't, really.
http://eclipsesource.com/blogs/2013/01/23/how-to-track-lifecycle-changes-...
i can file for events after my plugin is started, but most errors will occur during resolution (which is before my checkup bundle is started). Only way to get around that is to use BundleWatcher, which requires vm props / config.ini changes to be installed when osgi is first starting up... and so is not suitable for JBT.
so i guess we're stuck with reading logs ;)
> 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
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4113) uninstaller folder is empty after installation is done
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4113:
-----------------------------------
Summary: uninstaller folder is empty after installation is done
Key: JBDS-4113
URL: https://issues.jboss.org/browse/JBDS-4113
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.2.0.AM2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.2.0.AM2
After installation uninstaller folder is empty and there is error message in install.log file
{code}
Thu, 13 Oct 2016 23:52:18 GMT-ERROR: Data - Error: ENOENT: no such file or directory, lstat 'C:\p\rh\dpi\transpiled\browser\uninstaller\uninstall.ps1'
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ]
Rob Stryker updated JBDS-4095:
------------------------------
Fix Version/s: 10.2.0.AM2
> 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: Dmitrii Bocharov
> 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
(v6.4.11#64026)
9 years, 5 months