July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22748) No Integration Stack connectors found in JBT 4.4.1.AM2 / devstudio 10.0.1.AM2 Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22748?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22748: ------------------------------- Description: Nothing in the Eclipse console reporting errors discovering connectors. But as you can see, the links in ide-config.properties to the JBT integration stack bits are somewhat borked. was: Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): {code} No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! An exception stack trace is not available. {code} {code} All attempts to discover connectors have failed An exception stack trace is not available. 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) {code} > No Integration Stack connectors found in JBT 4.4.1.AM2 / devstudio 10.0.1.AM2 Central > ------------------------------------------------------------------------------------- > > Key: JBIDE-22748 > URL: https://issues.jboss.org/browse/JBIDE-22748 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: 22737.png, 22737_2.png > > > Nothing in the Eclipse console reporting errors discovering connectors. > But as you can see, the links in ide-config.properties to the JBT integration stack bits are somewhat borked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22748) No Integration Stack connectors found in JBT 4.4.1.AM2 / devstudio 10.0.1.AM2 Central

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22748: ---------------------------------- Summary: No Integration Stack connectors found in JBT 4.4.1.AM2 / devstudio 10.0.1.AM2 Central Key: JBIDE-22748 URL: https://issues.jboss.org/browse/JBIDE-22748 Project: Tools (JBoss Tools) Issue Type: Bug Components: central-update Affects Versions: 4.4.1.AM2 Reporter: Marián Labuda Assignee: Nick Boldt Priority: Critical Fix For: 4.4.1.AM2 Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): {code} No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! An exception stack trace is not available. {code} {code} All attempts to discover connectors have failed An exception stack trace is not available. 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) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22737) No connectors found for Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22737?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22737: ------------------------------------ Note that I installed BYOE feature from https://devstudio.jboss.com/10.0/snapshots/updates/ and Community Central feature from http://download.jboss.org/jbosstools/neon/snapshots/updates/ to verify the above and produce screenshots. > No connectors found for Central > ------------------------------- > > Key: JBIDE-22737 > URL: https://issues.jboss.org/browse/JBIDE-22737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: 22737.png, 22737_2.png > > > Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > An exception stack trace is not available. > {code} > {code} > All attempts to discover connectors have failed > An exception stack trace is not available. > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22737) No connectors found for Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22737?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22737: ------------------------------- Attachment: 22737_2.png 22737.png Please, in future, take the time to state which VERSION of devstudio or jbosstools you're using to see the issue. Helps me psychic-debug the issue. :D In JBoss Tools... {code} org.jboss.tools.foundation.core_1.3.1.AM1-v20160708-0436-B1041.jar org.jboss.tools.community.central_2.1.1.v20160614-2133.jar org.jboss.tools.central_2.1.1.v20160711-1005 {code} ... [^22737.png] In Devstudio... {code} com.jboss.devstudio.core.central_10.0.1.AM2-v20160715-1111-B5661.jar org.jboss.tools.central_2.1.1.v20160711-1005 {code} ... [^22737_2.png] > No connectors found for Central > ------------------------------- > > Key: JBIDE-22737 > URL: https://issues.jboss.org/browse/JBIDE-22737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: 22737.png, 22737_2.png > > > Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > An exception stack trace is not available. > {code} > {code} > All attempts to discover connectors have failed > An exception stack trace is not available. > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22737) No connectors found for Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22737?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22737. ------------------------------ Verified my fix works, so closing. > No connectors found for Central > ------------------------------- > > Key: JBIDE-22737 > URL: https://issues.jboss.org/browse/JBIDE-22737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: 22737.png, 22737_2.png > > > Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > An exception stack trace is not available. > {code} > {code} > All attempts to discover connectors have failed > An exception stack trace is not available. > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22737) No connectors found for Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22737?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22737. -------------------------------- Fix Version/s: 4.4.1.AM2 Resolution: Done I believe this should fix the problem: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/6b0060... > No connectors found for Central > ------------------------------- > > Key: JBIDE-22737 > URL: https://issues.jboss.org/browse/JBIDE-22737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM2 > > > Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > An exception stack trace is not available. > {code} > {code} > All attempts to discover connectors have failed > An exception stack trace is not available. > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22731) Query.getReturnAliases() is deprecated and needs to be worked around

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22731?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22731. ------------------------------- Resolution: Done > Query.getReturnAliases() is deprecated and needs to be worked around > -------------------------------------------------------------------- > > Key: JBIDE-22731 > URL: https://issues.jboss.org/browse/JBIDE-22731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > > IQuery.getReturnAliases() delegates to the core Hibernate Query.getReturnAliases() which is deprecated and returns a 'null' result. A workaround is needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22731) Query.getReturnAliases() is deprecated and needs to be worked around

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22731?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-22731: --------------------------------- Assignee: Koen Aers > Query.getReturnAliases() is deprecated and needs to be worked around > -------------------------------------------------------------------- > > Key: JBIDE-22731 > URL: https://issues.jboss.org/browse/JBIDE-22731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > > IQuery.getReturnAliases() delegates to the core Hibernate Query.getReturnAliases() which is deprecated and returns a 'null' result. A workaround is needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-577) Servers How To: Configure IDE for use with Docker

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-577?page=com.atlassian.jira.plug... ] Alexey Kazakov commented on TOOLSDOC-577: ----------------------------------------- [~xcoulon] please take a look. > Servers How To: Configure IDE for use with Docker > ------------------------------------------------- > > Key: TOOLSDOC-577 > URL: https://issues.jboss.org/browse/TOOLSDOC-577 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide > Affects Versions: 4.2.1.Final > Reporter: Michelle Murray > Assignee: Misha Ali > Labels: Basics, Docker > > For info see: > * https://goldmann.pl/blog/2013/11/20/developing-with-wildfly-jboss-develop... > * http://www.mastertheboss.com/eclipse/jboss-eclipse/eclipse-useful-tips-an... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-346) If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-346: --------------------------------------- Summary: If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703] Key: ERT-346 URL: https://issues.jboss.org/browse/ERT-346 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot We use feature in node that we can put out modules in a “node_modules” in a parent folder and it will be properly found: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_fol... Node is working properly but if I add a breakpoint in a source file inside “node_modules” the breakpoint does not get hit. To reproduce the issue: 1. Create a JavaScript project “test”. 2. Add a file “test.js” to the project with content: var m1 = require("m1"); console.log("m1.myFunc = " + m1.myFunc(3)); 3. Create a JavaScript project called “node_modules”. 4. Add a folder “m1” to the project “node_modules”. 5. Add a file “index.js” to the folder “m1” with content: module.exports.myFunc = function( i) { return i*i; } 6. Debug “test.js” as Node – it works. Node is finding property “index.js”. 7. Add a breakpoint to “index.js”. 8. Debug “test.js” as Node – it runs, but the breakpoint does not suspend the target. Is there workaround for this issues? Most of our projects are relying on the “node_modules” being found in the parent folder. That is making most of our code hard to debug. I tested this on Ubuntu 14.04. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016