April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-19719: ------------------------------------------- Assignee: Max Rydahl Andersen (was: Gorkem Ercan) > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- OK, [~snjeza], I understand it can find the properties file in the structure, but I still don't quite understand how it found it in my other installations of JBDS - clearly it cannot search your whole disk during the p2 installation to find any instances of Eclipse/JBDS and the properties files. So it seems to me it searches everything under ECLIPSE_HOME/../* ? Meaning it will search all other Eclipse or JBDS installs in the same directory as your currently running Eclipse? > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19291: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > "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-19438) Module is not in Started state after deploy even though it is deployed correctly - 4.3.x

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19438?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19438. --------------------------------- Verified in JBDS 9.0.0.Alpha2 BYOE. > Module is not in Started state after deploy even though it is deployed correctly - 4.3.x > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19438 > URL: https://issues.jboss.org/browse/JBIDE-19438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > When deploying project to running server (I've tried it with Wildfly 8 and EAP 6.3), the project remains in state [Synchronized] instead of [Started, Synchronized] even though the project is correctly deployed and running. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19532: --------------------------------------- I tried your steps, Rob, and for some odd reason when I open the symlink in the Browse dialog (your step 5), it will automatically take me to the linked dir - apparently that's how the OS works. In Terminal, I can cd to the symlink and it will act as a directory. But in Finder / Open File dialog if I double click an item which is a symlink to a directory, it will take me to the target directory. So I end up which the actual path in the "Server base directory" field and there is no error. But if I manually enter the path with the symlink, it will validate the config properly: {code} /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final_sym/standalone {code} If I change one character, it will show the error saying it can't find the config. If I fix the path again, the error will disappear. So for me it works correctly. And the server starts ok, too - it will contain this parameter: -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final_sym/standalone > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen edited comment on JBTIS-431 at 4/29/15 3:58 AM: -------------------------------------------------------------------- Just to grok this - does this mean Designer 9.x is backwards compatible from a user perspective been using JBDS 8.0 and upwards ? i.e. Designer 9 does not remove any features or support for runtimes that been targeted since JBDS 8.0 ? was (Author: maxandersen): Just to grok this - does this mean Designer 9.x is backwards compatible from a user perspective been using JBDS 8.0 and upwards ? i.e. Designer 9 does not remove any features or support for runtimes that been targeted with JBDS 8.0 ? > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-431: ------------------------------------------- Just to grok this - does this mean Designer 9.x is backwards compatible from a user perspective been using JBDS 8.0 and upwards ? i.e. Designer 9 does not remove any features or support for runtimes that been targeted with JBDS 8.0 ? > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3395) JBDS Installer should let to include additional features and provide panel to select for installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3395?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3395. ----------------------------- Verified for 9.0.0 Alpha2, closing > JBDS Installer should let to include additional features and provide panel to select for installation > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-3395 > URL: https://issues.jboss.org/browse/JBDS-3395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Alpha2 > > > Installer should let include additional p2 repositories and provide the way to select additional features (IU's) during installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18786) Bump LiveReload version to 1.3.0 on master branch

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18786?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-18786. ------------------------------- Verified for 4.3.0 Alpha1, closing > Bump LiveReload version to 1.3.0 on master branch > ------------------------------------------------- > > Key: JBIDE-18786 > URL: https://issues.jboss.org/browse/JBIDE-18786 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18787) Build failures with Mars M3 TP

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18787?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-18787. ------------------------------- The build succeeds, closing > Build failures with Mars M3 TP > ------------------------------- > > Key: JBIDE-18787 > URL: https://issues.jboss.org/browse/JBIDE-18787 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > In relation with JBIDE-18748. > There are compilation errors because of API changes in the TP (using Servlet-API 3.1 now) -- 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 April 2015