October 2016 - jbosstools-issues - Jboss List Archives

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-23331) Maven New and Noteworthy for 4.4.2.AM2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23331?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-23331. ------------------------------- Resolution: Rejected Nothing new here. > Maven New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23331 > URL: https://issues.jboss.org/browse/JBIDE-23331 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Jeff MAURY > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Maven JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Maven by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Maven4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Maven for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23342) Project Examples New and Noteworthy for 4.4.2.AM2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23342?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-23342. ------------------------------- Resolution: Rejected Nothing new here. > Project Examples New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23342 > URL: https://issues.jboss.org/browse/JBIDE-23342 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Jeff MAURY > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Project Examples JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Project Examples, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Project Examples by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Project Examples4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Project Examples for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23338) Central New and Noteworthy for 4.4.2.AM2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23338?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-23338. ------------------------------- Resolution: Rejected Nothing new here. > Central New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23338 > URL: https://issues.jboss.org/browse/JBIDE-23338 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Jeff MAURY > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Central by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Central4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

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 October 2016