October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15770) Can't remove cordova plugins with "remove cordova plugin" menu item

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15770?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-15770: ----------------------------------------- All of them? Specifically I had added cordova camera, battery, contacts, and two blackberry ones. > 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 > > "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, 6 months

1
0
0 / 0

[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: -------------------------------------- Can you recall which plugin failed to remove? > 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 > > "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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-200) Update missing JBTIS TP dependencies

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-200?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-200: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/pull/138 > Update missing JBTIS TP dependencies > ------------------------------------ > > Key: JBTIS-200 > URL: https://issues.jboss.org/browse/JBTIS-200 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.5.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > Detected by: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-4.1.p2.directo... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Add aerogear.hybrid amd vpe.*sim features to JBoss Central + JBDS update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2733: ----------------------------- Summary: Add aerogear.hybrid amd vpe.*sim features to JBoss Central + JBDS update site (was: Make Cordova tooling and CordovaSim ready to be available from software/update tab ) > Add aerogear.hybrid amd vpe.*sim features to JBoss Central + JBDS update site > ----------------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Fix For: 7.1.0.Beta1 > > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Add aerogear.hybrid amd vpe.*sim features to JBoss Central + JBDS update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2733: ---------------------------------- Blocked by JBDS-2812, which has PRs on it awaiting review by [~maxandersen]. > Add aerogear.hybrid amd vpe.*sim features to JBoss Central + JBDS update site > ----------------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Fix For: 7.1.0.Beta1 > > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15718) Add blank icon to align JBoss Welcome screen columns

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15718?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-15718: ----------------------------------- Assignee: Fred Bricon > Add blank icon to align JBoss Welcome screen columns > ---------------------------------------------------- > > Key: JBIDE-15718 > URL: https://issues.jboss.org/browse/JBIDE-15718 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Catherine Robson > Assignee: Fred Bricon > Priority: Trivial > > It really bothers me that the columns on JBoss Central do not properly align horizontally. Can we add a blank icon that links nowhere to the headers of "Tutorial" and "Other Resources" so these sections horizontally align with the sections to the left? > See areas of concern in screenshot: > https://www.evernote.com/shard/s230/sh/d7467a14-e89a-42d0-955c-d40a65e506... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15718) Add blank icon to align JBoss Welcome screen columns

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15718?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15718: -------------------------------- Fix Version/s: 4.1.1.CR1 > Add blank icon to align JBoss Welcome screen columns > ---------------------------------------------------- > > Key: JBIDE-15718 > URL: https://issues.jboss.org/browse/JBIDE-15718 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Catherine Robson > Assignee: Fred Bricon > Priority: Trivial > Fix For: 4.1.1.CR1 > > > It really bothers me that the columns on JBoss Central do not properly align horizontally. Can we add a blank icon that links nowhere to the headers of "Tutorial" and "Other Resources" so these sections horizontally align with the sections to the left? > See areas of concern in screenshot: > https://www.evernote.com/shard/s230/sh/d7467a14-e89a-42d0-955c-d40a65e506... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15780) Unable to create Richfaces project with EAP runtime

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-15780: ---------------------------------------- Summary: Unable to create Richfaces project with EAP runtime Key: JBIDE-15780 URL: https://issues.jboss.org/browse/JBIDE-15780 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.1.1.Beta1 Reporter: Rastislav Wagner Priority: Blocker Fix For: 4.1.1.Beta1 {code} java.lang.IllegalArgumentException: Bad artifact coordinates org.jboss.bom:jboss-javaee-6.0-with-tools:pom:1.0.0.M12-redhat-1::, expected format is <groupId>:<artifactId>[:<type>[:<classifier>]]:<version> at org.jboss.tools.maven.core.MavenUtil.createArtifact(MavenUtil.java:197) at org.jboss.tools.maven.core.internal.resolution.ArtifactResolutionService.isResolved(ArtifactResolutionService.java:57) at org.jboss.tools.maven.project.examples.utils.MavenArtifactHelper.checkEnterpriseRequirementsAvailable(MavenArtifactHelper.java:100) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.checkEnterpriseProperty(ArchetypeExamplesWizardPage.java:318) at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.validate(ArchetypeExamplesWizardPage.java:298) at org.jboss.tools.maven.project.examples.wizard.xpl.MavenProjectWizardArchetypeParametersPage$1.modifyText(MavenProjectWizardArchetypeParametersPage.java:155) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) at org.eclipse.swt.widgets.Combo.setText(Combo.java:2038) at org.eclipse.m2e.core.ui.internal.wizards.ResolverConfigurationComponent.loadData(ResolverConfigurationComponent.java:132) at org.eclipse.m2e.core.ui.internal.wizards.AbstractMavenWizardPage.setVisible(AbstractMavenWizardPage.java:107) at org.jboss.tools.maven.project.examples.wizard.xpl.MavenProjectWizardArchetypeParametersPage.setVisible(MavenProjectWizardArchetypeParametersPage.java:546) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238) at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:615) at org.jboss.tools.central.editors.GettingStartedPage.access$11(GettingStartedPage.java:606) at org.jboss.tools.central.editors.GettingStartedPage$5.linkActivated(GettingStartedPage.java:578) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2813) JPA Hibernate validation rules are too strict by default

by Tomas Remes (JIRA)

Tomas Remes created JBDS-2813: --------------------------------- Summary: JPA Hibernate validation rules are too strict by default Key: JBDS-2813 URL: https://issues.jboss.org/browse/JBDS-2813 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: hibernate Affects Versions: 7.1.0.Alpha2, 7.0.0.GA Reporter: Tomas Remes When you for example import Seam UI example (https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/ui) to JBDS, you will face a lot of IMO unnecessary errors, which are fired by JPA validator. E.g: "Target entity is not defined" These rules are in most cases defined as optional attributes of JPA annotations, therefore I think the validation rules are too strict - many of them have error level by default. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2813) JPA Hibernate validation rules are too strict by default

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/JBDS-2813?page=com.atlassian.jira.plugin.... ] Tomas Remes commented on JBDS-2813: ----------------------------------- You can check this related issue for more details. > JPA Hibernate validation rules are too strict by default > -------------------------------------------------------- > > Key: JBDS-2813 > URL: https://issues.jboss.org/browse/JBDS-2813 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: hibernate > Affects Versions: 7.0.0.GA, 7.1.0.Alpha2 > Reporter: Tomas Remes > > When you for example import Seam UI example (https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/ui) to JBDS, you will face a lot of IMO unnecessary errors, which are fired by JPA validator. E.g: > "Target entity is not defined" > These rules are in most cases defined as optional attributes of JPA annotations, therefore I think the validation rules are too strict - many of them have error level by default. -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2013