May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3408: ---------------------------------- That's just the download stats tracker. Are you saying we should disable that when the network can't be found? > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-640: ------------------------------- Sprint: 2015/S9 (27-Apr > 10-May) (was: 2015/S10 (11-May -> 24-May) 2) > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-640: ------------------------------------ Proposed fix text for JBDS: Note: Before attempting to install or create a hybrid mobile project with JBoss Developer Studio, ensure that the Android SDK is installed and up to date. Creating or installing hybrid mobile projects without a working and updated installation of Android SDK can result in unexpected errors. Proposed fix text for JBT: Note: Before attempting to install or create a hybrid mobile project with JBoss Tools, ensure that the Android SDK is installed and up to date. Creating or installing hybrid mobile projects without a working and updated installation of Android SDK can result in unexpected errors. Any thoughts on the text/suggestions for improvement for relevance, [~ldimaggio]? > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-641) How-to configure a remote server with JBDS 8.1

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-641: ---------------------------------- Summary: How-to configure a remote server with JBDS 8.1 Key: TOOLSDOC-641 URL: https://issues.jboss.org/browse/TOOLSDOC-641 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Components: General documentation issues Affects Versions: 4.2.3.Final Reporter: Misha Ali Assignee: Martin Malina Fix For: 4.2.3.Final Requesting QE review for the following content: https://docs.google.com/a/redhat.com/document/d/1sd5_RaThCjbRxeA4D-YcYjXL... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work with remote server docs missing

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-620: ------------------------------------ Thanks to Max's tip about using localhost as the "remote" server, this is now complete and tested and ready for review. Creating a new QA subtask for Martin with the following link: https://docs.google.com/a/redhat.com/document/d/1sd5_RaThCjbRxeA4D-YcYjXL... > How to work with remote server docs missing > ------------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-640: ---------------------------------- Assignee: Misha Ali (was: Supriya Bharadwaj) > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-640: ---------------------------------- Assignee: Supriya Bharadwaj (was: Misha Ali) Sprint: 2015/S10 (11-May -> 24-May) 2 > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19291: -------------------------------- Comment: was deleted (was: After a lot of digging, it seems this is not being thrown on our contribution, but rather the earlyStartup in the org.eclipse.jst.ws.jaxws.utils plugin. If you browse your Mars M6 folder, and run the following: {code} unzip -c plugins/org.eclipse.jst.ws.jaxws.utils_1.0.300.v201308151836.jar plugin.xml {code} It will display the contents of that plugins' plugin.xml file, which read: {code} <plugin> <extension point="org.eclipse.ui.startup"> <startup></startup> </extension> </plugin> {code} We can see their startup lacks a 'class' attribute. This is your culprit. ) > "Unable to execute early startup code ..." exception after starup. > ------------------------------------------------------------------ > > Key: JBIDE-19291 > URL: https://issues.jboss.org/browse/JBIDE-19291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > After startup in error log there is this error: > {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19291: ------------------------------------- After a lot of digging, it seems this is not being thrown on our contribution, but rather the earlyStartup in the org.eclipse.jst.ws.jaxws.utils plugin. If you browse your Mars M6 folder, and run the following: {code} unzip -c plugins/org.eclipse.jst.ws.jaxws.utils_1.0.300.v201308151836.jar plugin.xml {code} It will display the contents of that plugins' plugin.xml file, which read: {code} <plugin> <extension point="org.eclipse.ui.startup"> <startup></startup> </extension> </plugin> {code} We can see their startup lacks a 'class' attribute. This is your culprit. > "Unable to execute early startup code ..." exception after starup. > ------------------------------------------------------------------ > > Key: JBIDE-19291 > URL: https://issues.jboss.org/browse/JBIDE-19291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > After startup in error log there is this error: > {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19291. --------------------------------- Resolution: Done http://git.eclipse.org/c/webservices/webtools.webservices.jaxws.git/commi... This was fixed 3 days ago in their master. > "Unable to execute early startup code ..." exception after starup. > ------------------------------------------------------------------ > > Key: JBIDE-19291 > URL: https://issues.jboss.org/browse/JBIDE-19291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > After startup in error log there is this error: > {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.} > org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found. > at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288) > at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015