[JBoss JIRA] (JBIDE-16152) Support multiselection when removing cordova plugins via project explorer
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16152?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-16152:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 4.2.x
(was: 4.1.1.Final)
> Support multiselection when removing cordova plugins via project explorer
> -------------------------------------------------------------------------
>
> Key: JBIDE-16152
> URL: https://issues.jboss.org/browse/JBIDE-16152
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Environment: JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> Reporter: Vlado Pakan
> Priority: Minor
> Fix For: 4.2.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create new Hybrid Mobile project
> 2. Add couple of plug-ins to project
> 3. Select added plugins in Project Explorer
> 4. Choose Remove Cordova Plug-in from Project Explorer context menu
> Error: Dialog asking to remove first selected plug-in is displayed and only this plug-in is removed. Would be more intuitive if all selected plug-ins will be removed
--
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, 4 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2801:
-------------------------------------
Based on discussion with [~nickboldt] and [~maxandersen] there shouldn't be any steps needed for the users to be able to update from JBDS 7.0.x to 7.1.0, just Help -> Check for updates. But this will not work for updates in central.
{quote}
nboldt: maxandersen1: yes, but updates/7.0/ does not include GWT
[5:13pm] nboldt: updates/7.0/ only has JBDS + TP and the TP doesn't include GWT
[5:14pm] nboldt: so you can see the new JBDS product feature and perform the update, including getting Kepler SR1 instead of Kepler R
[5:14pm] psrna is now known as psrna_afk.
[5:14pm] nboldt: but I'm not 100% if you'll see updates to central. Also not sure if having existing connector installed will show up as "already installed" even if there's a newer version
[5:14pm] nboldt: we need to test that
{quote}
I will check tomorrow what happens when there is new content in central available.
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {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, 4 months
[JBoss JIRA] (JBIDE-16152) Support multiselection when removing cordova plugins via project explorer
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-16152:
-----------------------------------
Summary: Support multiselection when removing cordova plugins via project explorer
Key: JBIDE-16152
URL: https://issues.jboss.org/browse/JBIDE-16152
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: aerogear-hybrid
Affects Versions: 4.1.1.CR1
Environment: JBDS7.1.0.CR1 CR1-v20131124-0717-B560
Reporter: Vlado Pakan
Priority: Minor
Fix For: 4.1.1.Final
1. Create new Hybrid Mobile project
2. Add couple of plug-ins to project
3. Select added plugins in Project Explorer
4. Choose Remove Cordova Plug-in from Project Explorer context menu
Error: Dialog asking to remove first selected plug-in is displayed and only this plug-in is removed. Would be more intuitive if all selected plug-ins will be removed
--
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, 4 months
[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14629:
----------------------------------------
Fix Version/s: 4.1.2
(was: 4.1.1.Final)
> Errors when creating and deploying seam2 project with Seam 2.3.Final
> ---------------------------------------------------------------------
>
> Key: JBIDE-14629
> URL: https://issues.jboss.org/browse/JBIDE-14629
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.x, 4.1.2
>
> Attachments: seamerror.png
>
>
> ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB.
> 1. Fix DefaultDS Database connection definition
> ASSERT: It's possible to connect to DefaultDS
> 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final
> ERROR: There is error in Problems view:
> !seamerror.png!
> 3. Start seam project on server
> ERROR: This error appear in Server log. Application is not deployed:
> {noformat}
> 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found.
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml")
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war")
> 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar")
> 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource]
> {noformat}
> Is this supported scenario?
--
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, 4 months