[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ]
Denis Golovin resolved JBIDE-15304.
-----------------------------------
Resolution: Done
> NullPointerExceptions in JAX-RS doesn't report what project is affected
> -----------------------------------------------------------------------
>
> Key: JBIDE-15304
> URL: https://issues.jboss.org/browse/JBIDE-15304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.0.Alpha1, 4.1.1.Alpha2
>
>
> I've seen this exception happens many times when I have several projects imported out of JBoss Central:
> {code}java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105)
> at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69)
> at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178)
> at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114)
> at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136)
> at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105)
> at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406)
> at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173)
> {code}
> couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15304:
----------------------------------
Steps to Reproduce:
1. Import HTML 5 project from JBoss Central
2. Check there is no exceptions in Error Log View
> NullPointerExceptions in JAX-RS doesn't report what project is affected
> -----------------------------------------------------------------------
>
> Key: JBIDE-15304
> URL: https://issues.jboss.org/browse/JBIDE-15304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> I've seen this exception happens many times when I have several projects imported out of JBoss Central:
> {code}java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105)
> at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69)
> at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178)
> at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114)
> at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136)
> at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105)
> at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406)
> at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173)
> {code}
> couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16088) Compilation error when building WebServices against Luna TP
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16088?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-16088:
---------------------------------------
[~bfitzpat],
Yes, which is why I always add the '-fae' arg. But in my case, the test suite *hangs* just after an empty Eclipse shell opened.
Do you have the same problem on your machine ?
> Compilation error when building WebServices against Luna TP
> -----------------------------------------------------------
>
> Key: JBIDE-16088
> URL: https://issues.jboss.org/browse/JBIDE-16088
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, webservices
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
>
> I have the following dependency resolution problem when building the Web Services component against the Luna TP:
> {code}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.6.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.ws.creation.core 1.6.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.ws.creation.core 1.6.0.qualifier requires 'bundle org.apache.ant [1.8.2,1.9.0)' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15779) Plugin removed via config.xml editor is not removed from <project>/plugins directory
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15779?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15779:
--------------------------------------
released to 4.1.1 branch
> Plugin removed via config.xml editor is not removed from <project>/plugins directory
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-15779
> URL: https://issues.jboss.org/browse/JBIDE-15779
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> Steps to reproduce:
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file, add some feature on tab. Platform Properties and save
> ASSERT: Respective plugins are added to project plugins directory
> 3, Remove added feature from config.xml file similar way as in point 2.
> ERROR: Removed plugin is still in plugins directory. When project is built for Android via calling menu Run As > Run on Android Emulator. This plugin is added to built project and it's not correct
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15779) Plugin removed via config.xml editor is not removed from <project>/plugins directory
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15779?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-15779.
----------------------------------
Resolution: Done
> Plugin removed via config.xml editor is not removed from <project>/plugins directory
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-15779
> URL: https://issues.jboss.org/browse/JBIDE-15779
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> Steps to reproduce:
> 1. Create new Hybrid Mobile project
> 2. Open project config.xml file, add some feature on tab. Platform Properties and save
> ASSERT: Respective plugins are added to project plugins directory
> 3, Remove added feature from config.xml file similar way as in point 2.
> ERROR: Removed plugin is still in plugins directory. When project is built for Android via calling menu Run As > Run on Android Emulator. This plugin is added to built project and it's not correct
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16081) Aerogear.hybrid requires org.eclipse.debug.core [3.7.0, 3.9.0) but Luna includes 3.9.0
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16081?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-16081.
----------------------------------
Release Notes Text: released to 4.1.1.x
Resolution: Done
> Aerogear.hybrid requires org.eclipse.debug.core [3.7.0,3.9.0) but Luna includes 3.9.0
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-16081
> URL: https://issues.jboss.org/browse/JBIDE-16081
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Labels: respin-a
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: install-all-of-JBT-into-LunaM3-except-aerogear.hybrid-error-details.png, install-all-of-JBT-into-LunaM3-except-aerogear.hybrid.png
>
>
> If org.jboss.tools.aerogear.hybrid.ios.core could be changed to depend on org.eclipse.debug.core [3.7.0,3.10.0) then it could be installed into Luna M3.
> 1. fire up Eclipse Standard Luna M3 package (eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz). Help > Install new > ...
> * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... (JBT 4.1.1.CR1 TP site)
> * http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ )JBT 4.1.1.CR1 Core update site)
> uncheck "group by category" then select all features, and you'll get this:
> !install-all-of-JBT-into-LunaM3-except-aerogear.hybrid.png!
> !install-all-of-JBT-into-LunaM3-except-aerogear.hybrid-error-details.png!
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
> Software currently installed: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
> Only one of the following can be installed at once:
> Debug Core 3.9.0.v20131003-1341 (org.eclipse.debug.core 3.9.0.v20131003-1341)
> Debug Core 3.9.0.v20130819-1716 (org.eclipse.debug.core 3.9.0.v20130819-1716)
> Debug Core 3.9.0.v20130731-1644 (org.eclipse.debug.core 3.9.0.v20130731-1644)
> Debug Core 3.8.0.v20130514-0954 (org.eclipse.debug.core 3.8.0.v20130514-0954)
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK 2.1.0.20131103-0830 (epp.package.standard 2.1.0.20131103-0830)
> To: org.eclipse.epp.package.standard.feature.feature.group [2.1.0.20131103-0830]
> Cannot satisfy dependency:
> From: Eclipse Standard/SDK Feature 2.1.0.20131103-0830 (org.eclipse.epp.package.standard.feature.feature.group 2.1.0.20131103-0830)
> To: org.eclipse.platform.feature.group [4.4.0.v20131030-2000]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.4.0.v20131030-2000 (org.eclipse.platform.feature.group 4.4.0.v20131030-2000)
> To: org.eclipse.debug.core [3.9.0.v20131003-1341]
> Cannot satisfy dependency:
> From: JBoss Hybrid Mobile Application Development Tools (Experimental) 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.feature.feature.group 1.0.100.CR1-v20131116-0025-B52)
> To: org.jboss.tools.aerogear.hybrid.ios.core [1.0.100.CR1-v20131116-0025-B52]
> Cannot satisfy dependency:
> From: JBoss Hybrid Mobile App. Dev. iOS Core 1.0.100.CR1-v20131116-0025-B52 (org.jboss.tools.aerogear.hybrid.ios.core 1.0.100.CR1-v20131116-0025-B52)
> To: bundle org.eclipse.debug.core [3.7.0,3.9.0)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16053) Aerogear: backbutton listener doesn't work on the android device
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16053?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-16053.
----------------------------------
Release Notes Text: released to 4.1.1 branch
Resolution: Done
> Aerogear: backbutton listener doesn't work on the android device
> ----------------------------------------------------------------
>
> Key: JBIDE-16053
> URL: https://issues.jboss.org/browse/JBIDE-16053
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.CR1, 4.1.1.Final
>
>
> http://docs.phonegap.com/en/3.1.0/cordova_events_events.md.html#backbutton - backbutton event doc
> Steps for verifying:
> 1. Create new Hybrid Mobile Application Project
> 2. Update index.html with the sample from the documentation:
> {code:title=index.html|borderStyle=solid}
> <!DOCTYPE html>
> <html>
> <head>
> <title>Back Button Example</title>
> <script type="text/javascript" charset="utf-8" src="cordova.js"></script>
> <script type="text/javascript" charset="utf-8">
> // Wait for device API libraries to load
> //
> function onLoad() {
> document.addEventListener("deviceready", onDeviceReady, false);
> }
> // device APIs are available
> //
> function onDeviceReady() {
> // Register the event listener
> document.addEventListener("backbutton", onBackKeyDown, false);
> }
> // Handle the back button
> //
> function onBackKeyDown() {
> alert(1);
> }
> </script>
> </head>
> <body onload="onLoad()">
> </body>
> </html>
> {code}
> 3. Run the app on the android device
> 4. Press the back button when the app will be ready
> 5. ERROR: App will be closed - no alert will be shown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15865) Add Progress Dialog when opening Cordova Plug-in Discovery Dialog
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15865?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15865:
---------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.1.1.CR1)
> Add Progress Dialog when opening Cordova Plug-in Discovery Dialog
> -----------------------------------------------------------------
>
> Key: JBIDE-15865
> URL: https://issues.jboss.org/browse/JBIDE-15865
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.Alpha1
>
>
> 1. Create Hybrid Mobile Project
> 2. Open config.xml file in Cordova Configuration Editor
> 3. Select tab Platform Properties and click to add Features
> It takes couple of seconds to open Cordova Plug-in Discovery Dialog and user doesn't know what's going on. At the begining mouse cursor is in state waiting but latter it's state is normal for couple of seconds but dialog is still not open.
> Would be nice to inform users what's going on when opening this dialog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months