October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBTIS-529: ----------------------------------- OK, so the Fuse wizard is now hidden when EA is disabled (close/reopen central to see it happen). Now looking into problem #2... > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integraiotn Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3551: --------------------------------- Component/s: docker (was: jsp/jsf/xml/html-source-editing) > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3551: ------------------------------------ Assignee: Xavier Coulon (was: Alexey Kazakov) > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21024) webservice tester "forgets" parameterized url

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21024?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21024: ----------------------------------- Fix Version/s: 4.3.x 4.4.x > webservice tester "forgets" parameterized url > --------------------------------------------- > > Key: JBIDE-21024 > URL: https://issues.jboss.org/browse/JBIDE-21024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.x, 4.4.x > > > use html5 kitchensink example and one of the urls you can run is "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/{id:..." > When you run this webservice tester will ask you about id - great. > But when executing the first time it will reset the url to "http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members/" meaning it is not possible to run again without manually typing it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21025?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21025: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > hibernate querying nor content assist is broken > ----------------------------------------------- > > Key: JBIDE-21025 > URL: https://issues.jboss.org/browse/JBIDE-21025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > using html5-kitchensink I cannot get basic content assist to work. > "from Member m where m.|" gives no content assist at all. > And trying to run the query results in: > {code} > java.lang.NullPointerException > at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845) > at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24) > at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169) > at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) > at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21029) Use newer Easymport (update TP)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-21029: -------------------------------------- Assignee: Mickael Istria > Use newer Easymport (update TP) > ------------------------------- > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20... > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21029) Use newer Easymport (update TP)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21029?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21029: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > Use newer Easymport (update TP) > ------------------------------- > > Key: JBIDE-21029 > URL: https://issues.jboss.org/browse/JBIDE-21029 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final > *Reason:* Use new features and fixes (allowing preview of import plan) > *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 0.2.0 > *License and owner:* EPL, Red Hat Inc. > *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20... > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-playground > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21029) Use newer Easymport (update TP)

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-21029: -------------------------------------- Summary: Use newer Easymport (update TP) Key: JBIDE-21029 URL: https://issues.jboss.org/browse/JBIDE-21029 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: easymport, target-platform Affects Versions: 4.3.1.Beta1 Reporter: Mickael Istria Newer builds of Easymport framework contain important changes that fixes issues reported against 4.3.0.Final *Reason:* Use new features and fixes (allowing preview of import plan) *Project page/sources:* https://wiki.eclipse.org/E4/UI/Smart_Import *Version:* 0.2.0 *License and owner:* EPL, Red Hat Inc. *Original p2 repo:* http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui/ *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/e4.ui/0.2.0.v20... *Include Sources:* Yes *Affected JBoss Tools components:* jbosstools-playground *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3549 at 10/27/15 1:40 PM: -------------------------------------------------------------- I think that you will also want some (visual) way in the IDE to determine the current status of the CDK. was (Author: ldimaggio): I think that yo > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3549: ------------------------------------ I think that yo > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 2015