[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-23208 at 9/21/16 1:43 PM:
------------------------------------------------------------------------
The date is stored in preferences by X509CertificateParser where it is converted from Date to String by getValidity(X509Certificate).
The validity of dates retrieved from preferences is checked in SSLCertificatesPreference.isValid(String).
These methods match until default Locale is changed on computer. The problem can be fixed by explicitely setting in both these places English locale:
{code}
SimpleDateFormat dateFormat = new SimpleDateFormat(X509CertificateParser.DATE_FORMAT, Locale.ENGLISH);
{code}
However, to provide for the backword compatibility, the check SSLCertificatesPreference.isValid(String) should for a couple of versions try both default and English locales.
Another solution might be storing dates not in a date format but as a long integer returned by Date.getTime().
was (Author: scabanovich):
The date is stored in preferences by X509CertificateParser where it is converted from Date to String by getValidity(X509Certificate).
The validity of dates retrieved from preferences is checked in SSLCertificatesPreference.isValid(String).
These methods match until default Locale is changed on computer. The problem can be fixed by explicitely setting in both these places English locale:
{code}
SimpleDateFormat dateFormat = new SimpleDateFormat(X509CertificateParser.DATE_FORMAT, Locale.ENGLISH);
{code}
However, to provide for the backword compatibility, the check SSLCertificatesPreference.isValid(String) should for a couple of versions try both default and English locales.
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23208:
-----------------------------------------------
The date is stored in preferences by X509CertificateParser where it is converted from Date to String by getValidity(X509Certificate).
The validity of dates retrieved from preferences is checked in SSLCertificatesPreference.isValid(String).
These methods match until default Locale is changed on computer. The problem can be fixed by explicitely setting in both these places English locale:
{code}
SimpleDateFormat dateFormat = new SimpleDateFormat(X509CertificateParser.DATE_FORMAT, Locale.ENGLISH);
{code}
However, to provide for the backword compatibility, the check SSLCertificatesPreference.isValid(String) should for a couple of versions try both default and English locales.
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4055) Bundles should "import-package" javax.servlet
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4055?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4055:
--------------------------------------
[~xcoulon] can you please fix it for 4.4.2.AM1?
> Bundles should "import-package" javax.servlet
> ---------------------------------------------
>
> Key: JBDS-4055
> URL: https://issues.jboss.org/browse/JBDS-4055
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Mat Booth
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 10.2.0.AM1
>
>
> I have an environment where I am using a different implementation of javax.servlet 3.1.0 that has a different bundle symbolic name.
> Because of this, some jboss bundles that use "Require-Bundle" fail to load with errors like the following:
> {code}
> !ENTRY org.jboss.tools.livereload.core 4 0 2016-09-21 18:08:45.542
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1176]
> Unresolved requirement: Require-Bundle: javax.servlet; bundle-version="3.1.0"
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Ideally, these dependencies should be specified instead with "Import-Package" as recommended by OSGi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4055) Bundles should "import-package" javax.servlet
by Mat Booth (JIRA)
[ https://issues.jboss.org/browse/JBDS-4055?page=com.atlassian.jira.plugin.... ]
Mat Booth commented on JBDS-4055:
---------------------------------
The offending bundle is "org.jboss.tools.livereload.core" but the test bundle "org.jboss.tools.livereload.test" probably also should be fixed.
> Bundles should "import-package" javax.servlet
> ---------------------------------------------
>
> Key: JBDS-4055
> URL: https://issues.jboss.org/browse/JBDS-4055
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Mat Booth
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 10.2.0.AM1
>
>
> I have an environment where I am using a different implementation of javax.servlet 3.1.0 that has a different bundle symbolic name.
> Because of this, some jboss bundles that use "Require-Bundle" fail to load with errors like the following:
> {code}
> !ENTRY org.jboss.tools.livereload.core 4 0 2016-09-21 18:08:45.542
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1176]
> Unresolved requirement: Require-Bundle: javax.servlet; bundle-version="3.1.0"
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Ideally, these dependencies should be specified instead with "Import-Package" as recommended by OSGi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23016:
-------------------------------------
I believe this should be fixed by the recent terminal changes JBIDE-23039
I'll leave this open to investigate once landrush looks set to be re-added.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.2.AM1
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4055) Bundles should "import-package" javax.servlet
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4055?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4055:
------------------------------------
Assignee: Xavier Coulon (was: Alexey Kazakov)
> Bundles should "import-package" javax.servlet
> ---------------------------------------------
>
> Key: JBDS-4055
> URL: https://issues.jboss.org/browse/JBDS-4055
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Mat Booth
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 10.2.0.AM1
>
>
> I have an environment where I am using a different implementation of javax.servlet 3.1.0 that has a different bundle symbolic name.
> Because of this, some jboss bundles that use "Require-Bundle" fail to load with errors like the following:
> {code}
> !ENTRY org.jboss.tools.livereload.core 4 0 2016-09-21 18:08:45.542
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1176]
> Unresolved requirement: Require-Bundle: javax.servlet; bundle-version="3.1.0"
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Ideally, these dependencies should be specified instead with "Import-Package" as recommended by OSGi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4055) Bundles should "import-package" javax.servlet
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4055?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4055:
---------------------------------
Priority: Critical (was: Major)
> Bundles should "import-package" javax.servlet
> ---------------------------------------------
>
> Key: JBDS-4055
> URL: https://issues.jboss.org/browse/JBDS-4055
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Mat Booth
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 10.2.0.AM1
>
>
> I have an environment where I am using a different implementation of javax.servlet 3.1.0 that has a different bundle symbolic name.
> Because of this, some jboss bundles that use "Require-Bundle" fail to load with errors like the following:
> {code}
> !ENTRY org.jboss.tools.livereload.core 4 0 2016-09-21 18:08:45.542
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1176]
> Unresolved requirement: Require-Bundle: javax.servlet; bundle-version="3.1.0"
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Ideally, these dependencies should be specified instead with "Import-Package" as recommended by OSGi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4055) Bundles should "import-package" javax.servlet
by Mat Booth (JIRA)
Mat Booth created JBDS-4055:
-------------------------------
Summary: Bundles should "import-package" javax.servlet
Key: JBDS-4055
URL: https://issues.jboss.org/browse/JBDS-4055
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Sub-task
Components: livereload
Reporter: Mat Booth
Assignee: Alexey Kazakov
I have an environment where I am using a different implementation of javax.servlet 3.1.0 that has a different bundle symbolic name.
Because of this, some jboss bundles that use "Require-Bundle" fail to load with errors like the following:
{code}
!ENTRY org.jboss.tools.livereload.core 4 0 2016-09-21 18:08:45.542
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1176]
Unresolved requirement: Require-Bundle: javax.servlet; bundle-version="3.1.0"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
Ideally, these dependencies should be specified instead with "Import-Package" as recommended by OSGi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23039:
-------------------------------
Labels: cdk new_and_noteworthy (was: )
> Need an interactive terminal that fits specific requirements
> ------------------------------------------------------------
>
> Key: JBIDE-23039
> URL: https://issues.jboss.org/browse/JBIDE-23039
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: cdk, new_and_noteworthy
> Fix For: 4.4.2.AM1
>
> Attachments: vagranttty.png
>
>
> CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for.
> 1) I must be able to get a Process or IProcess object when a command is run
> 2) I must be able to get an event or know when the process terminates
> 3) The terminal or console must be interactive and allow user input when prompted.
> 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins.
> These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
> 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input.
> 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
> a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
> b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
> 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed.
> Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant.
> Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream?
> No other obvious solutions have presented themselves in the past year.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months