[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-19532:
-----------------------------------
Assignee: Denis Golovin (was: Rob Stryker)
> "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
>
>
> 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
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19697:
---------------------------------------
This is the old code assuming the following JBDS file structure:
JBDS_HOME/runtimes
JBDS_HOME/studio
JBDS_HOME/studio/features
JBDS_HOME/studio/plugins
JBDS_HOME/studio/configuration
In your case, Eclipse has found EAP 6.3 in one of the following directories:
/Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha1-java8/studio/runtime_locations.properties
/Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha2-24/studio/runtime_locations.properties
See also JBIDE-19713.
> 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
[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-19725:
--------------------------------------
Assigning to [~mickael_istria] so that he can have the pleasure to explain "Easymport" is in fact correct..
[~mickael_istria] we do not use "aerogear" on user visible strings.. It is Hybrid Mobile for user strings.
> EasyImport plugin title misspelled
> ----------------------------------
>
> Key: JBIDE-19725
> URL: https://issues.jboss.org/browse/JBIDE-19725
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-platform
> Affects Versions: 4.3.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Mickael Istria
> Attachments: import.png
>
>
> The plugin name is spelled as:
> JBoss Easymport for Aerogear
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-19728:
--------------------------------------
These are not aerogear dialogs. [~mickael_istria] Do you know the correct component for easy import
> Easy Import - The first and second screens in the dialog should be merged into one
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-19728
> URL: https://issues.jboss.org/browse/JBIDE-19728
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid, integration-platform
> Affects Versions: 4.3.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Mickael Istria
> Attachments: import_1.png, import_2.png
>
>
> See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported.
> Why not simply skip the first screen and start with the second?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-19726:
---------------------------------
Component/s: aerogear-hybrid
(was: integration-platform)
> Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19726
> URL: https://issues.jboss.org/browse/JBIDE-19726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Alpha2
> Reporter: Len DiMaggio
>
> Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI
> !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882
> !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar
> !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882
> !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js
> !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882
> !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ]
Len DiMaggio reassigned JBIDE-19726:
------------------------------------
Assignee: Gorkem Ercan
> Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19726
> URL: https://issues.jboss.org/browse/JBIDE-19726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Gorkem Ercan
>
> Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI
> !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882
> !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar
> !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882
> !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js
> !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882
> !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months