[JBoss JIRA] (JBDS-2802) Investigate use of SpringIDE 3.4 in JBT/JBDS Central
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2802?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2802:
-------------------------------------
[~nickboldt] and [~mlabuda] please allow me to introduce myself. My name is Joshua and I am [~marius.bogoevici] replacement. I am working as the Snowdrop lead, integrating Spring with JBoss.
I have been working to update the Spring Archetype and several [Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts]. I am trying to resolve the errors that I am finding in JDBS/Eclipse. I think I can explain some of what you have seen or at least try to bring clarity in reproducing the errors. I would say that the Quickstarts provide some good test "examples" for you too.
ERRORs:
The error in jboss-deployment-structure.xml is based on the xsd being improperly written. There are several Jira's written on it but WFLY-943 best describes it and the solution. So this is one we just need to live with for now.
(If you don't build with Eclipse then most of the errors don't appear, but what fun is that. So in order to see the following errors you need to Build.)
The "Build path is incomplete. Cannot find class file for org/aspect/weave" error only appears in the JBDS version with the Spring IDE installed. If you switch to an Eclipse install that has both JBoss and Spring IDE installed and then build, these errors go away. From what I have found is might have to do with the AspectJ Compiler and AspectJ Development Tools not being installed in the JDBS version of the Spring IDE.
The "Build path is incomplete. Cannot find class file for javax/servlet/ServletContext" error appears to me to be an m2e issue though I am not entirely sure. I do know that if I "Add External JARs" to the "Java Build Path" and select the modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar it fixes this error. I do think this is just a work around. The reason that I think this is an m2e issue is that any project with this error builds fine on the CLI because the jar is supplied by the BOM. If you look at the Effective Pom tab of the pom.xml you will find the servlet jar present. Alternatively this can be fixed by adding the servlet jar listed in the BOM that you find in the Effective Pom tab. But that means editing the actual project to fix an IDE based error.
If there is anything else I can do to help, please let me know.
> Investigate use of SpringIDE 3.4 in JBT/JBDS Central
> ----------------------------------------------------
>
> Key: JBDS-2802
> URL: https://issues.jboss.org/browse/JBDS-2802
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Affects Versions: 7.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Marián Labuda
>
> New mirror for SpringIDE 3.4.0.201310051539-RELEASE:
> http://download.jboss.org/jbosstools/updates/requirements/springide/3.4.0...
--
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-15795) Support multiselection of Feature in Cordova Configuration Editor for config.xml file
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15795?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15795:
--------------------------------------
This can possibly be supported on removals from context menu but not on the config.xml editor. Removals from config.xml editor has inconsistency problems that may make this feature confusing
> Support multiselection of Feature in Cordova Configuration Editor for config.xml file
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-15795
> URL: https://issues.jboss.org/browse/JBIDE-15795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Would be nice to support multiselection of feature in Cordova Configuration Editor when removing features from project configuration.
> User scenario:
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> 3. Add more Features
> 4. Select more Features
> 5. Click on button remove
> ASSERT: All selected features are removed from project configuration
--
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-15795) Support multiselection of Feature in Cordova Configuration Editor for config.xml file
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15795?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-15795.
----------------------------------
Resolution: Won't Fix
> Support multiselection of Feature in Cordova Configuration Editor for config.xml file
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-15795
> URL: https://issues.jboss.org/browse/JBIDE-15795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Would be nice to support multiselection of feature in Cordova Configuration Editor when removing features from project configuration.
> User scenario:
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> 3. Add more Features
> 4. Select more Features
> 5. Click on button remove
> ASSERT: All selected features are removed from project configuration
--
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-15795) Support multiselection of Feature in Cordova Configuration Editor for config.xml file
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15795?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15795:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: (was: 4.1.1.CR1)
> Support multiselection of Feature in Cordova Configuration Editor for config.xml file
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-15795
> URL: https://issues.jboss.org/browse/JBIDE-15795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Minor
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Would be nice to support multiselection of feature in Cordova Configuration Editor when removing features from project configuration.
> User scenario:
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file in Cordova Configuration Editor
> 3. Add more Features
> 4. Select more Features
> 5. Click on button remove
> ASSERT: All selected features are removed from project configuration
--
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-15770) Can't remove cordova plugins with "remove cordova plugin" menu item
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15770?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15770:
--------------------------------------
released a fix to master to use a busy indicator instead of a progress dialog.
> Can't remove cordova plugins with "remove cordova plugin" menu item
> -------------------------------------------------------------------
>
> Key: JBIDE-15770
> URL: https://issues.jboss.org/browse/JBIDE-15770
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
>
> "Remove Cordova plugin" menu item doesn't work.
> 1. Make a hybrid mobile project with wizard
> 2. Add a cordova plugin via the Cordova Configuration Editor, Platform Properties pane, Add button >> plug-ins listed in Project Explorer tab under plugins folder
> 4. Right-click plug-in name (in Project Explorer)
> 5. Click Remove Cordova Plugin >> window flashes open and closes immediately, plug-in still listed under plugin folder :(
--
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 edited comment on JBIDE-15779 at 11/1/13 7:28 PM:
---------------------------------------------------------------
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the xml bits. Also since name is not guaranteed to be unique like ID is we also always present a confirmation dialog where ID is present before removing a plugin.
You can see a great example of this with the device-motion plugin.
was (Author: gercan):
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the xml bits. Also since name is not guaranteed to be unique like ID is we also always present a confirmation dialog where ID is present before removing a plugin.
> 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
> 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 edited comment on JBIDE-15779 at 11/1/13 7:29 PM:
---------------------------------------------------------------
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the config.xml bits. Also since name is not guaranteed to be unique like ID is we also always present a confirmation dialog where ID is present before removing a plugin.
You can see a great example of this with the device-motion plugin.
was (Author: gercan):
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the xml bits. Also since name is not guaranteed to be unique like ID is we also always present a confirmation dialog where ID is present before removing a plugin.
You can see a great example of this with the device-motion plugin.
> 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
> 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 edited comment on JBIDE-15779 at 11/1/13 7:29 PM:
---------------------------------------------------------------
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the config.xml bits. Also since name is not guaranteed to be unique like ID is, we also always present a confirmation dialog where ID is present before removing a plugin.
You can see a great example of this with the device-motion plugin.
was (Author: gercan):
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the config.xml bits. Also since name is not guaranteed to be unique like ID is we also always present a confirmation dialog where ID is present before removing a plugin.
You can see a great example of this with the device-motion plugin.
> 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
> 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 commented on JBIDE-15779:
--------------------------------------
Released a fix for this on master. But note that removing a plugin from config editor may not always give the expected results. Let me explain.
A plugin is identified by its id on the cordova land. However on the config.xml instead of ID a name is used to identify a plugin. By convention, the name matches the name of the plugin (which is different from id) however there are cases where the name of the plugin and the name inserted to config.xml does not match. In those cases we fall back and just remove the xml bits. Also since name is not guaranteed to be unique like ID is we also always present a confirmation dialog where ID is present before removing a plugin.
> 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
> 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