[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21831:
----------------------------------------
If CDK server doesn't use it then it should not complain about a wrong hostname )
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
> Attachments: new-cdk-server.png
>
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21780) Cordova projects exported as native projects fails to run in iOS simulator under XCode
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21780?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-21780:
---------------------------------
Story Points: 1
> Cordova projects exported as native projects fails to run in iOS simulator under XCode
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-21780
> URL: https://issues.jboss.org/browse/JBIDE-21780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins when exported as native projects appear to have incorrect locations set for config.xml.
> A new config.xml appears to be created with default content and none of the Cordova plugins in the configuration, which is incorrect. In addition, the original config.xml file is created/copied into the www/ directory, which is ignored by the build and/or runtime.
> When the native project is run in the iOS simulator, it shows errors/warnings that indicate failure in initialising Cordova. Plugins like the Device plugin are not loaded since they cannot be found in the config.xml (assuming the newly created config is overridding the original config), resulting in a failed application start.
> The output window shows the following message:
> {{ERROR: Plugin 'Device' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21781?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-21781:
---------------------------------
Story Points: 1
> Running Cordova projects with Cordova plugins fails on iOS simulators
> ---------------------------------------------------------------------
>
> Key: JBIDE-21781
> URL: https://issues.jboss.org/browse/JBIDE-21781
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS.
> This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator.
> Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported:
> {{deviceready has not fired after 5 seconds.}}
> {{Channel not fired: onCordovaInfoReady}}
> which indicates that Cordova failed to initialise.
> As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w...
> In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}.
> A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21780) Cordova projects exported as native projects fails to run in iOS simulator under XCode
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21780?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-21780:
---------------------------------
Sprint: devex #4 March 2016
> Cordova projects exported as native projects fails to run in iOS simulator under XCode
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-21780
> URL: https://issues.jboss.org/browse/JBIDE-21780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins when exported as native projects appear to have incorrect locations set for config.xml.
> A new config.xml appears to be created with default content and none of the Cordova plugins in the configuration, which is incorrect. In addition, the original config.xml file is created/copied into the www/ directory, which is ignored by the build and/or runtime.
> When the native project is run in the iOS simulator, it shows errors/warnings that indicate failure in initialising Cordova. Plugins like the Device plugin are not loaded since they cannot be found in the config.xml (assuming the newly created config is overridding the original config), resulting in a failed application start.
> The output window shows the following message:
> {{ERROR: Plugin 'Device' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21781?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-21781:
---------------------------------
Sprint: devex #4 March 2016
> Running Cordova projects with Cordova plugins fails on iOS simulators
> ---------------------------------------------------------------------
>
> Key: JBIDE-21781
> URL: https://issues.jboss.org/browse/JBIDE-21781
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS.
> This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator.
> Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported:
> {{deviceready has not fired after 5 seconds.}}
> {{Channel not fired: onCordovaInfoReady}}
> which indicates that Cordova failed to initialise.
> As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w...
> In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}.
> A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21865) Fix jbosstools-server build from master
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21865?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21865:
--------------------------------------
Assignee: Rob Stryker
> Fix jbosstools-server build from master
> ---------------------------------------
>
> Key: JBIDE-21865
> URL: https://issues.jboss.org/browse/JBIDE-21865
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> With latest version from master build fails with compilation errors:
> {code}[INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure:
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[26]
> [INFO] [ERROR] public class ModuleLaunchConfigurationProvider implements ILaunchConfigurationProvider {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The type ModuleLaunchConfigurationProvider must implement the inherited abstract method ILaunchConfigurationProvider.supports(ILaunchDescriptor, ILaunchTarget)
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[26]
> [INFO] [ERROR] public class ModuleLaunchConfigurationProvider implements ILaunchConfigurationProvider {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The type ModuleLaunchConfigurationProvider must implement the inherited abstract method ILaunchConfigurationProvider.getLaunchConfiguration(ILaunchDescriptor, ILaunchTarget)
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[26]
> [INFO] [ERROR] public class ModuleLaunchConfigurationProvider implements ILaunchConfigurationProvider {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The type ModuleLaunchConfigurationProvider must implement the inherited abstract method ILaunchConfigurationProvider.launchTargetRemoved(ILaunchTarget)
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[26]
> [INFO] [ERROR] public class ModuleLaunchConfigurationProvider implements ILaunchConfigurationProvider {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The type ModuleLaunchConfigurationProvider must implement the inherited abstract method ILaunchConfigurationProvider.getLaunchConfigurationType(ILaunchDescriptor, ILaunchTarget)
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[48]
> [INFO] [ERROR] public boolean supports(ILaunchDescriptor descriptor, IRemoteConnection target) throws CoreException {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The method supports(ILaunchDescriptor, IRemoteConnection) of type ModuleLaunchConfigurationProvider must override or implement a supertype method
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[57]
> [INFO] [ERROR] public ILaunchConfigurationType getLaunchConfigurationType(ILaunchDescriptor descriptor, IRemoteConnection target)
> [INFO] [ERROR] throws CoreException {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The method getLaunchConfigurationType(ILaunchDescriptor, IRemoteConnection) of type ModuleLaunchConfigurationProvider must override or implement a supertype method
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[63]
> [INFO] [ERROR] public ILaunchConfiguration getLaunchConfiguration(ILaunchDescriptor descriptor, IRemoteConnection target)
> [INFO] [ERROR] throws CoreException {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The method getLaunchConfiguration(ILaunchDescriptor, IRemoteConnection) of type ModuleLaunchConfigurationProvider must override or implement a supertype method
> [INFO] [ERROR] C:\P\rh\jbds\jbosstools-server\wtp\plugins\org.jboss.tools.wtp.server.launchbar\src\org\jboss\tools\wtp\server\launchbar\ModuleLaunchConfigurationProvider.java:[109]
> [INFO] [ERROR] public void launchTargetRemoved(IRemoteConnection target) throws CoreException {
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [INFO] [ERROR] The method launchTargetRemoved(IRemoteConnection) of type ModuleLaunchConfigurationProvider must override or implement a supertype method
> [INFO] [ERROR] 8 problems (8 errors)
> [INFO] [ERROR] -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build with the command
> [INFO] [ERROR] mvn <goals> -rf :org.jboss.tools.wtp.server.launchbar
> [INFO] ..FAILED (974.1 s)
> [INFO] The build exited with code 1. See c:\P\rh\jbds\jbosstools-dev\full-build\..\..\jbosstools-dev\build.log for details.
> [INFO] -------------------------------------------------{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-45) Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-45?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-45:
----------------------------
Sprint: devex #4 March 2016
> Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
> --------------------------------------------------------------------------------
>
> Key: ERT-45
> URL: https://issues.jboss.org/browse/ERT-45
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
>
> Chromium JavaScript Debugger by default expose scripts loaded in JavaScript VM through virtual file system. It looks like normal workspace project with name matches the launch configuration name.
> All interactions with VM are done through actions available on files in that virtual system.
> Ideally that virtual FS should not be exposed to user if project that targeted for debug is already presented in workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years