May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13562) Repository is synchronized but adapter states [Started, Republish]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13562?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-13562. --------------------------------------- Resolution: Duplicate Issue > Repository is synchronized but adapter states [Started, Republish] > ------------------------------------------------------------------ > > Key: JBIDE-13562 > URL: https://issues.jboss.org/browse/JBIDE-13562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > Attachments: console.png, server.png > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2538) JBDS70_0319: [Commit] (?) (P1) JDK Warning in Add Server/Start Server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2538?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-2538. ------------------------------- Resolution: Done A warning is added to the new runtime wizard in the case where the user has chosen "Default" vm. In the case the user has chosen a specific VM which is NOT a jdk, an error is shown in the wizard. When launching, if the server requires a jdk but is using a jre, an error is shown. (CoreException thrown, error handled by wtp). > JBDS70_0319: [Commit] (?) (P1) JDK Warning in Add Server/Start Server > --------------------------------------------------------------------- > > Key: JBDS-2538 > URL: https://issues.jboss.org/browse/JBDS-2538 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Rob Stryker > Priority: Blocker > Fix For: 7.0.0.Beta2 > > > EAP requires JDK - when adding a server, start server, warn the user that a JDK is needed. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13401) Cannot binary deploy to EWS OpenShift application out of the box

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13401?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13401: ---------------------------------------- Summary: Cannot binary deploy to EWS OpenShift application out of the box (was: Cannot binary deploy to EWS OpenShift application) > Cannot binary deploy to EWS OpenShift application out of the box > ---------------------------------------------------------------- > > Key: JBIDE-13401 > URL: https://issues.jboss.org/browse/JBIDE-13401 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 3.3.2.Final > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > > EWS application type uses for deployments folder 'webapps' instead of 'deployments' as JBoss AS7/EAP6. The Server Adapter sets directory for deployments to <app>/deployments but in this case it is <app>/webapps. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13020) Have to prompt user to upload keys like we do when no domain

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13020?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13020: ------------------------------------- Priority: Major (was: Minor) > Have to prompt user to upload keys like we do when no domain > ------------------------------------------------------------ > > Key: JBIDE-13020 > URL: https://issues.jboss.org/browse/JBIDE-13020 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: create-domain-first.png, no-keys-yet.png > > > We currently error in the git configuration page of the application wizard if the user did not add any keys to his OpenShift account: > !no-keys-yet.png! > He can then hit the "SSH Keys Wizard" link, get to the ssh keys management wizard and upload a key. The error will then go away and the user can process, create/import his application. > We should not error, we should prompt the user to upload keys if we see that he has none (on OpenShift) so far. We do the very same with the domain. If the user launches the wizard, he'll get a dialog that asks him to create a domain. The application wizard will only appear on successfull creation of the domain. > !create-domain-first.png! -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13765) Over active warning detector

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13765?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-13765. --------------------------------- Resolution: Partially Completed If you add <m2e.jpa.activation>false</m2e.jpa.activation> to your pom properties, the JPA configurator won't install the JPA Facet when using [m2e-wtp 1.0.0|http://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/1.0.0#Enable.2FD...]. Without that facet, the JPA validator won't be activated. That's the best we can do without going real dirty. > Over active warning detector > ---------------------------- > > Key: JBIDE-13765 > URL: https://issues.jboss.org/browse/JBIDE-13765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.0.0.Final > Environment: Was testing in JBDS 6 > Reporter: Jason Porter > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > Link to the deltaspike quickstart https://github.com/jboss-jdf/jboss-as-quickstart/tree/master/deltaspike-b... > Coming from Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=919361 -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13003: ---------------------------------- Fix Version/s: 4.1.0.Beta2 (was: 4.1.0.Beta1) > No support for inheritance in JAX-RS API scan > --------------------------------------------- > > Key: JBIDE-13003 > URL: https://issues.jboss.org/browse/JBIDE-13003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.0.0.Alpha2 > Reporter: Ron Ratovsky > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta2 > > > Assume: > class BaseRest { > @POST > public Response save(Object o) { > .... > } > } > @Path("/url") > class RealRest extends BaseRest {} > The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview. > While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14410) Maven Test class importing internal class JBossASHandler

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14410?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14410: -------------------------------- Assignee: Snjezana Peco (was: Fred Bricon) > Maven Test class importing internal class JBossASHandler > -------------------------------------------------------- > > Key: JBIDE-14410 > URL: https://issues.jboss.org/browse/JBIDE-14410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.0.Beta1 > > > ./jbosstools-central/maven/tests/org.jboss.tools.maven.sourcelookup.test/src/org/jboss/tools/maven/sourcelookup/test/SourceLookupTest.java has the following method: > {code} > private static IRuntimeDetectorDelegate getJBossASHandler() { > Set<IRuntimeDetector> detectors = RuntimeCoreActivator.getDefault().getRuntimeDetectors(); > for (IRuntimeDetector detector:detectors) { > IRuntimeDetectorDelegate delegate = ((RuntimeDetector)detector).getDelegate(); > if (delegate instanceof JBossASHandler) { > return delegate; > } > } > return null; > } > {code} > The class and its package name are not technically API. It would be best if you instead compared against the handler's id: org.jboss.tools.runtime.handlers.JBossASHandler > Since this ID is declared in plugin.xml, it's best if you hard-code the string. > Trying to clean up people who depend on my internal classes so that I can get to organizing stuff properly. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13728) JSF facet is not enabled for maven project with seam-faces dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13728?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-13728. --------------------------------- Fix Version/s: 4.1.0.Beta1 (was: 4.1.0.Beta2) Resolution: Done Fixed with https://github.com/jbosstools/jbosstools-central/commit/e096ca8bf3d3e82fe... Seam Faces and now Deltaspike Faces dependencies trigger the installation of the JSF 2.0 Facet > JSF facet is not enabled for maven project with seam-faces dependency > --------------------------------------------------------------------- > > Key: JBIDE-13728 > URL: https://issues.jboss.org/browse/JBIDE-13728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > see JBIDE-8755 -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13728) JSF facet is not enabled for maven project with seam-faces dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13728?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-13728 at 5/14/13 5:30 AM: -------------------------------------------------------------- Fixed with https://github.com/jbosstools/jbosstools-central/commit/e096ca8bf3d3e82fe... Seam Faces and now Deltaspike Faces dependencies trigger the installation of the JSF 2.0 Facet, when the CDI Maven configurator and WTP 1.0.0 are installed. was (Author: fbricon): Fixed with https://github.com/jbosstools/jbosstools-central/commit/e096ca8bf3d3e82fe... Seam Faces and now Deltaspike Faces dependencies trigger the installation of the JSF 2.0 Facet > JSF facet is not enabled for maven project with seam-faces dependency > --------------------------------------------------------------------- > > Key: JBIDE-13728 > URL: https://issues.jboss.org/browse/JBIDE-13728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > see JBIDE-8755 -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14441) Forge: Remove Runtime button is always disabled in Installed Forge Runtimes Preference Page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14441?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-14441: --------------------------------------- {code}java.lang.ArrayIndexOutOfBoundsException: 0 at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.enableButtons(ForgeInstallationsPreferencePage.java:273) at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.access$3(ForgeInstallationsPreferencePage.java:262) at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$4.selectionChanged(ForgeInstallationsPreferencePage.java:169) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) at org.eclipse.jface.viewers.CheckboxTableViewer.handleSelect(CheckboxTableViewer.java:301) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) 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:3717) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3338) at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) 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:3717) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3338) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) 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:616) 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} > Forge: Remove Runtime button is always disabled in Installed Forge Runtimes Preference Page > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14441 > URL: https://issues.jboss.org/browse/JBIDE-14441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Denis Golovin > -- 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

13 years

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 May 2013