[JBoss JIRA] (JBDS-3957) No URL set for discovery catalog in central software/update
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3957?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3957:
---------------------------------
Fix Version/s: 10.0.1.M1
(was: 10.0.1.M2)
> No URL set for discovery catalog in central software/update
> -----------------------------------------------------------
>
> Key: JBDS-3957
> URL: https://issues.jboss.org/browse/JBDS-3957
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 10.0.1.M1
> Environment: devstudio-10.0.1.GA-v20160627-0436-B5620-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.1.M1
>
>
> When opening the central software/update page in nightly devstudio I'm getting the following errors:
> {noformat}
> No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {noformat}
> and
> {noformat}
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> After that the page is basically empty (no connectors, surprisingly). Only happens in devstudio, JBT nightly works fine for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3957) No URL set for discovery catalog in central software/update
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3957?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3957:
---------------------------------
Fix Version/s: 10.0.1.M2
Sprint: devex #117 July 2016
> No URL set for discovery catalog in central software/update
> -----------------------------------------------------------
>
> Key: JBDS-3957
> URL: https://issues.jboss.org/browse/JBDS-3957
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 10.0.1.M1
> Environment: devstudio-10.0.1.GA-v20160627-0436-B5620-installer-standalone.jar
> Reporter: Jan Richter
> Priority: Critical
> Fix For: 10.0.1.M1
>
>
> When opening the central software/update page in nightly devstudio I'm getting the following errors:
> {noformat}
> No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {noformat}
> and
> {noformat}
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> After that the page is basically empty (no connectors, surprisingly). Only happens in devstudio, JBT nightly works fine for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3957) No URL set for discovery catalog in central software/update
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3957?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3957:
---------------------------------
Priority: Critical (was: Major)
> No URL set for discovery catalog in central software/update
> -----------------------------------------------------------
>
> Key: JBDS-3957
> URL: https://issues.jboss.org/browse/JBDS-3957
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 10.0.1.M1
> Environment: devstudio-10.0.1.GA-v20160627-0436-B5620-installer-standalone.jar
> Reporter: Jan Richter
> Priority: Critical
>
> When opening the central software/update page in nightly devstudio I'm getting the following errors:
> {noformat}
> No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {noformat}
> and
> {noformat}
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> After that the page is basically empty (no connectors, surprisingly). Only happens in devstudio, JBT nightly works fine for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3957) No URL set for discovery catalog in central software/update
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3957?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3957:
--------------------------------------
cc: [~nickboldt], [~mickael_istria]
> No URL set for discovery catalog in central software/update
> -----------------------------------------------------------
>
> Key: JBDS-3957
> URL: https://issues.jboss.org/browse/JBDS-3957
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 10.0.1.M1
> Environment: devstudio-10.0.1.GA-v20160627-0436-B5620-installer-standalone.jar
> Reporter: Jan Richter
>
> When opening the central software/update page in nightly devstudio I'm getting the following errors:
> {noformat}
> No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {noformat}
> and
> {noformat}
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> After that the page is basically empty (no connectors, surprisingly). Only happens in devstudio, JBT nightly works fine for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20386) Autocompleation uses very outdated data
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20386?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20386:
-----------------------------------
Sprint: devex #117 July 2016
> Autocompleation uses very outdated data
> ---------------------------------------
>
> Key: JBIDE-20386
> URL: https://issues.jboss.org/browse/JBIDE-20386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.M2
>
>
> When you press Ctrl+Space after {{<#}} or in an expression after {{foo?}}, the list of directive names, and especially the list of built-in names shown is very outdated. Instead of maintaining these lists manually, the list of directive names could be get from {{freemarker.template.Configuration.getSupportedBuiltInDirectiveNames()}}, and the list of built-in names from {{Configuration.getSupportedBuiltInNames()}}.
> Some complication since 2.3.23 is that the list of names should be filtered based on {{Template.getActualNamingConvention()}} (which either returns {{Configuration.LEGACY_NAMING_CONVENTION}} or {{Configuration.CAMEL_CASE_NAMING_CONVENTION}}). Though the algorithm for that is simple: If a name contains upper case letter then it's camel case. Otherwise, if it contains {{_}} then it belongs to the legacy naming convention. Otherwise if it's a directive name that equals to a lower-cased camel case directive name, then it's legacy naming convention (consider {{elseIf}} VS {{elseif}}). Otherwise the name belongs to both naming conventions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22656) Related tag background becomes misplaced when typing
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22656?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22656:
-----------------------------------
Fix Version/s: 4.4.1.M2
(was: 4.4.x)
> Related tag background becomes misplaced when typing
> ----------------------------------------------------
>
> Key: JBIDE-22656
> URL: https://issues.jboss.org/browse/JBIDE-22656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.M2
>
>
> When you put the cursor inside an FTL tag, like {{<#if ...>}}, the background color of related tags, like {{<#else>}} and {{</#if>}}, is changed. The problem is that if now you start typing into a such background-colored tag, the offsets of the colored sections after it will become outdated, and so they start to drift left from under the tag. This is because the up to date offsets only become available after the reconciling thread has finished, but the background coloring logic is called directly in the keydown handler. I'm not familiar with plugin development, but I suspect this is architecturally wrong. Perhaps the reconciler should send some kind of event when it's done, and if the editor content is still in the state for which the reconciling was ran, only then should the old background coloring be removed and the new one is added.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22656) Related tag background becomes misplaced when typing
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22656?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22656:
-----------------------------------
Sprint: devex #117 July 2016
> Related tag background becomes misplaced when typing
> ----------------------------------------------------
>
> Key: JBIDE-22656
> URL: https://issues.jboss.org/browse/JBIDE-22656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.M2
>
>
> When you put the cursor inside an FTL tag, like {{<#if ...>}}, the background color of related tags, like {{<#else>}} and {{</#if>}}, is changed. The problem is that if now you start typing into a such background-colored tag, the offsets of the colored sections after it will become outdated, and so they start to drift left from under the tag. This is because the up to date offsets only become available after the reconciling thread has finished, but the background coloring logic is called directly in the keydown handler. I'm not familiar with plugin development, but I suspect this is architecturally wrong. Perhaps the reconciler should send some kind of event when it's done, and if the editor content is still in the state for which the reconciling was ran, only then should the old background coloring be removed and the new one is added.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20386) Autocompleation uses very outdated data
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20386?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20386:
-----------------------------------
Fix Version/s: 4.4.1.M2
(was: 4.3.x)
> Autocompleation uses very outdated data
> ---------------------------------------
>
> Key: JBIDE-20386
> URL: https://issues.jboss.org/browse/JBIDE-20386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.4.1.M2
>
>
> When you press Ctrl+Space after {{<#}} or in an expression after {{foo?}}, the list of directive names, and especially the list of built-in names shown is very outdated. Instead of maintaining these lists manually, the list of directive names could be get from {{freemarker.template.Configuration.getSupportedBuiltInDirectiveNames()}}, and the list of built-in names from {{Configuration.getSupportedBuiltInNames()}}.
> Some complication since 2.3.23 is that the list of names should be filtered based on {{Template.getActualNamingConvention()}} (which either returns {{Configuration.LEGACY_NAMING_CONVENTION}} or {{Configuration.CAMEL_CASE_NAMING_CONVENTION}}). Though the algorithm for that is simple: If a name contains upper case letter then it's camel case. Otherwise, if it contains {{_}} then it belongs to the legacy naming convention. Otherwise if it's a directive name that equals to a lower-cased camel case directive name, then it's legacy naming convention (consider {{elseIf}} VS {{elseif}}). Otherwise the name belongs to both naming conventions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20386) Autocompleation uses very outdated data
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20386?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20386:
--------------------------------------
Assignee: Alexey Kazakov (was: Denis Golovin)
> Autocompleation uses very outdated data
> ---------------------------------------
>
> Key: JBIDE-20386
> URL: https://issues.jboss.org/browse/JBIDE-20386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.M2
>
>
> When you press Ctrl+Space after {{<#}} or in an expression after {{foo?}}, the list of directive names, and especially the list of built-in names shown is very outdated. Instead of maintaining these lists manually, the list of directive names could be get from {{freemarker.template.Configuration.getSupportedBuiltInDirectiveNames()}}, and the list of built-in names from {{Configuration.getSupportedBuiltInNames()}}.
> Some complication since 2.3.23 is that the list of names should be filtered based on {{Template.getActualNamingConvention()}} (which either returns {{Configuration.LEGACY_NAMING_CONVENTION}} or {{Configuration.CAMEL_CASE_NAMING_CONVENTION}}). Though the algorithm for that is simple: If a name contains upper case letter then it's camel case. Otherwise, if it contains {{_}} then it belongs to the legacy naming convention. Otherwise if it's a directive name that equals to a lower-cased camel case directive name, then it's legacy naming convention (consider {{elseIf}} VS {{elseif}}). Otherwise the name belongs to both naming conventions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months