October 2015 - jbosstools-issues - Jboss List Archives

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

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-529: -------------------------------- Assignee: Fred Bricon > 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] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- That seems interesting! Did you try to deploy the same site with different BUILD_ALIAS to see whether both remain available on Nexus or if one would discard the other? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- 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 Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21025: ------------------------------------------- Summary: 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 Priority: Blocker 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-21024) webservice tester "forgets" parameterized url

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21024: ------------------------------------------- Summary: 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 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-21023) ctrl+shft+G sometimes give NPE in cdi tooling

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21023?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21023: -------------------------------------- Assignee: Daniel Azarov > ctrl+shft+G sometimes give NPE in cdi tooling > --------------------------------------------- > > Key: JBIDE-21023 > URL: https://issues.jboss.org/browse/JBIDE-21023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > used Ctrl+Shift+G on MemberService.java:@Inject validator from html5 kitchensink > gave me: > {code} > java.lang.NullPointerException > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.containsInSearchScope(InjectionPointQueryParticipant.java:69) > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:104) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) > at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21023) ctrl+shft+G sometimes give NPE in cdi tooling

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21023?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21023: ----------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > ctrl+shft+G sometimes give NPE in cdi tooling > --------------------------------------------- > > Key: JBIDE-21023 > URL: https://issues.jboss.org/browse/JBIDE-21023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > used Ctrl+Shift+G on MemberService.java:@Inject validator from html5 kitchensink > gave me: > {code} > java.lang.NullPointerException > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.containsInSearchScope(InjectionPointQueryParticipant.java:69) > at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:104) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) > at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21023) ctrl+shft+G sometimes give NPE in cdi tooling

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21023: ------------------------------------------- Summary: ctrl+shft+G sometimes give NPE in cdi tooling Key: JBIDE-21023 URL: https://issues.jboss.org/browse/JBIDE-21023 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Reporter: Max Rydahl Andersen used Ctrl+Shift+G on MemberService.java:@Inject validator from html5 kitchensink gave me: {code} java.lang.NullPointerException at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.containsInSearchScope(InjectionPointQueryParticipant.java:69) at org.jboss.tools.cdi.ui.search.InjectionPointQueryParticipant.search(InjectionPointQueryParticipant.java:104) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170) at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[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: ----------------------------------- So there are actually several problems here - fuse wizard/quickstarts show up even if EA is disabled: caused by only checking if IS update site is available, ignoring the EA flag. We can fix that server side - no connectors found when selecting the wizard: somehow the jboss.integration-stack.ea.bundle.fuse connector is not loaded apparently. I don't know why yet, need more investigation. Could be a problem either in JBT or JBTIS. - all fuse quickstarts show as having the fuse tooling installed when it's not. This is caused by an unfortunate hard coded id in https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu.... Ideally the whole requirement inference logic should be externalized, but the logic is not trivial, so it's a bit tricky. > 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 > 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] (JBTIS-529) fuse fails to install from jboss central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBTIS-529: -------------------------------------- cc: [~nickboldt], [~mickael_istria], [~pleacu] > 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 > 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] (JBTIS-529) fuse fails to install from jboss central

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-529: ----------------------------------------- Summary: 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 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

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