[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24960:
---------------------------------------
I can confirm that there is no warning or error when I import ejb-remote,
but where can I get ejb-security-jaas, [~mjurc]? I can't see it at https://github.com/jboss-developer/jboss-eap-quickstarts
> JBDS 11 produces warnings about missing schemas inconsistently
> --------------------------------------------------------------
>
> Key: JBIDE-24960
> URL: https://issues.jboss.org/browse/JBIDE-24960
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.5.0.Final
> Reporter: Michal Jurc
> Assignee: Rob Stryker
> Fix For: 4.5.1.Final
>
>
> The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart:
> ||Description||Resource||Path||Location||Type||
> |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem|
> The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it.
> This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-25263:
-----------------------------------------
By more debugging I've found out that the response code was 401 (Unauthorized). However, I do not know what caused it. After removing key in Preferences I was able to login successfully.
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-24671) [jbosstools-openshift] Block PRs for merge untill code is reviewed
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24671?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24671.
---------------------------------
Closing. Repository is set up.
> [jbosstools-openshift] Block PRs for merge untill code is reviewed
> ------------------------------------------------------------------
>
> Key: JBIDE-24671
> URL: https://issues.jboss.org/browse/JBIDE-24671
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.1.Final
>
> Attachments: bot-admin-openshift.png, protected-master-branch.png
>
>
> Nick asked:
> {quote}
> if we implement protected branches in github then no PRs can be merged w/o a PR review
> so for projects like Base or Server, this would slow Rob down as he'd be even more dependent on PR reviews
> for Openshift this would force Andre to break his PRs into smaller pieces so they could be more easily/quickly reviewed
> otherwise all forward dev would be halted
> so it's good from a "keep the code safe and clean" perspective
> but if we don't actually get buy-in / acceptance from the people who submit the PRs and review them, it will block progress{quote}
> Jeff replied:
> {quote}I think this make more sense for OpenShift as we are more in a collaborative way, I have the feeling that Rob is more or less alone in server. So let's start with OpenShift but I would see this after the GA{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25143) Server adapter wizard: details pane cuts off last entry and has repaint artifacts
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25143?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25143.
---------------------------------
Closing. It works as expected.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.1.0.GA
Build id: GA-v20171016-2315-B1387
Build date: 20171016-2315
> Server adapter wizard: details pane cuts off last entry and has repaint artifacts
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-25143
> URL: https://issues.jboss.org/browse/JBIDE-25143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Environment: Linux FC26, Gnome 3.24
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: server_adapter_wizard, ux
> Fix For: 4.5.1.Final
>
> Attachments: image-2017-10-04-10-53-51-136.png
>
>
> # EXEC: in OpenShift explorer: select a service and pick "Server adapter..." in the context menu
> # ASSERT server adapter wizard shows up
> # EXEC: look at the details panel (dont switch to any other window, keep the wizard dialog focused. Switching would have the repaint artifacts disappear)
> Result:
> It has repaint artifacts on the left border and the last entry in this particular case is cut off (Port)
> !image-2017-10-04-10-53-51-136.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25057) DEV_MODE should be enabled by default for all images when starting the server adapter in Run mode
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25057?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25057.
---------------------------------
Closing.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.1.0.GA
Build id: GA-v20171016-2315-B1387
Build date: 20171016-2315
> DEV_MODE should be enabled by default for all images when starting the server adapter in Run mode
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25057
> URL: https://issues.jboss.org/browse/JBIDE-25057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.1.AM3
>
>
> When the server adapter is started in Run mode, the deployment config is updated to enable the DEV_MODE only for NodeJS.
> I think this should be done for all images ( except for EAP ones which do not require because dev_mod (hot-deploy) is activated by default
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova updated JBIDE-25263:
------------------------------------
Issue Type: Enhancement (was: Feature Request)
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-25263:
---------------------------------------
Summary: OSIO Error refreshing token
Key: JBIDE-25263
URL: https://issues.jboss.org/browse/JBIDE-25263
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.5.1.AM3
Reporter: Lucia Jelinkova
When I called the OSIO service from Fabric8 plugin, the following error occurred.
{code:java}
org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25262) CDK server adapter: after removing ~/.minishift, server adapter can only be stopped via "Restart", "Stop" keeps it running
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25262?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25262:
-------------------------------------
Description:
steps:
# EXEC: in cmd line: setup cdk 3.2.alpha1 with a profile (ex. minishift setup-cdk --profile test42)
# EXEC: in "Servers" view: create a server adapter for this cdk with the profile and start it.
# EXEC: in cmd line: kill the ~/.minishift
# EXEC: in "Servers" view: select your server adapter and pick "Stop"
# ASSERT: "Console" view shows up pasting
{code}
You need to run 'minishift setup-cdk' first to install required CDK components.
{code}
And the following error dialog appears:
!image-2017-10-17-11-05-22-885.png!
# ASSERT: the server adapter is still **[Started]**
# EXEC: in "Servers" view: select your server adapter and pick "Restart"
# ASSERT: the same console (see above) output is shown, the same error dialog appears. You see the server adapter trying to start again but it fails, too
Result:
The server adapter is now in **[Stopped]**
was:
steps:
# EXEC: in cmd line: setup cdk 3.2.alpha1 with a profile (ex. minishift setup-cdk --profile test42)
# EXEC: in "Servers" view: create a server adapter for this cdk with the profile and start it.
# EXEC: in cmd line: kill the ~/.minishift
# EXEC: in "Servers" view: select your server adapter and pick "Stop"
# ASSERT: "Console" view shows up pasting
{code}
You need to run 'minishift setup-cdk' first to install required CDK components.
{code}
And the following error dialog appears:
!image-2017-10-17-11-05-22-885.png!
# ASSERT: the server adapter is still **[started]**
# EXEC: in "Servers" view: select your server adapter and pick "Restart"
# ASSERT: the same console (see above) output is shown, the same error dialog appears. You see the server adapter trying to start again but it fails, too
Result:
The server adapter is now in **[stopped]**
> CDK server adapter: after removing ~/.minishift, server adapter can only be stopped via "Restart", "Stop" keeps it running
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25262
> URL: https://issues.jboss.org/browse/JBIDE-25262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: image-2017-10-17-11-05-22-885.png
>
>
> steps:
> # EXEC: in cmd line: setup cdk 3.2.alpha1 with a profile (ex. minishift setup-cdk --profile test42)
> # EXEC: in "Servers" view: create a server adapter for this cdk with the profile and start it.
> # EXEC: in cmd line: kill the ~/.minishift
> # EXEC: in "Servers" view: select your server adapter and pick "Stop"
> # ASSERT: "Console" view shows up pasting
> {code}
> You need to run 'minishift setup-cdk' first to install required CDK components.
> {code}
> And the following error dialog appears:
> !image-2017-10-17-11-05-22-885.png!
> # ASSERT: the server adapter is still **[Started]**
> # EXEC: in "Servers" view: select your server adapter and pick "Restart"
> # ASSERT: the same console (see above) output is shown, the same error dialog appears. You see the server adapter trying to start again but it fails, too
> Result:
> The server adapter is now in **[Stopped]**
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months