June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20170) WebTools server adapter installer installs only a subset of what should be installed

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20170: ---------------------------------- Summary: WebTools server adapter installer installs only a subset of what should be installed Key: JBIDE-20170 URL: https://issues.jboss.org/browse/JBIDE-20170 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, server, updatesite, upstream Affects Versions: 4.3.0.Beta1 Reporter: Nick Boldt Assignee: Rob Stryker Priority: Critical Fix For: 4.3.0.Beta2 Steps to repro: {code}1. open clean Eclipse JEE 2. open Servers view 3. click 'No servers are avail... click to create new server..." 4. click "Download additional server adapters" 5. wait while the stuff loads. select "JBoss AS Server Adapter" or whatever it was called 6. wait as metadata loads again 7. click Next, accept license, etc. restart when prompted {code} Feature that should have been installed: {code:title=https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L99-L103} <feature id="org.jboss.ide.eclipse.as.feature"> <category name="org.eclipse.wst.server.core.serverAdapter"/> </feature> {code} Feature that instead gets installed: {code}org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta1-v20150612-2158-B25{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19178: ---------------------------------- Attachment: Console of 'App' with the pieces wired.png > Explorer: Add "Pipeline" view to OpenShift v3 explorer > ------------------------------------------------------ > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Console of 'App' with the pieces wired.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20095) openshift template does not warn/errror on required values

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20095?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20095: --------------------------------------- [~maxandersen] a) I suggested this before as a temporary fix but is square in line with annotations: add an annotation convention the specifies the list of required params or some known convention using multiple annotations that defines various missing metatdata about params. This will require by in from template writers. b) The CLI has a feature to delete by label which we could incorporate into JBT, but the only way to tie like things together is 1. Labels (prefered) 2. Fuzzy logic (e.g. figure out which services route to pods) - less desirable IMO 3. Impl multi-resource delete and let you delete the ones you added. (we have an open issue for this one) > openshift template does not warn/errror on required values > ---------------------------------------------------------- > > Key: JBIDE-20095 > URL: https://issues.jboss.org/browse/JBIDE-20095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.x > > > using https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v1beta3) a lot of variables are shown, click next/next and all is created except build configs stating "values are required" > 1) why am I not warned *Before* starting to create things ? > 2) why cannot undo/delete the things that was created but now useless since buildconfig not created ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-456) Establish an IS aggregate directory for use by Eclipse Marketplace

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-456: -------------------------------- Summary: Establish an IS aggregate directory for use by Eclipse Marketplace Key: JBTIS-456 URL: https://issues.jboss.org/browse/JBTIS-456 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.2.GA Reporter: Paul Leacu Assignee: Paul Leacu The Eclipse Marketplace installer reference URL must include JBDS core but the stabdard p2 update site URL must not. COnsequently - establish an aggregate that has both for EM. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20168: ------------------------------------ Seems that buildinfo.json reader isn't happy with my manually created json. So... maybe we need to rebuild xulrunner to use the latest parent pom & generate it: https://github.com/jbosstools/jbosstools-xulrunner/pull/15 > create buildinfo.json files for old project builds which predate buildinfo.json generator > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20168 > URL: https://issues.jboss.org/browse/JBIDE-20168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Max asked: > {quote} > i'm asking what shah's was used in the build for these components. > No sure if you are trolling me by us keeping having these conversations everytime we need to tag :) > Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right. > and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ? > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20166) Application wizard: Cannot create OpenShift v3 application from default template ruby-sample-helloworld

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20166?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20166: ------------------------------------------ this was merged and pushed to upstream/master. Resolving. > Application wizard: Cannot create OpenShift v3 application from default template ruby-sample-helloworld > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20166 > URL: https://issues.jboss.org/browse/JBIDE-20166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > > All resources, except buildconfig, are created for a new application from OpenShift v3 template ruby-sample-helloworld which is on OpenShift v3 server. While proceeding through wizard, there is a NPE invoked once "openshift" tree item in the wizard is selected. > {code} > java.lang.RuntimeException: java.lang.NullPointerException > at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:65) > at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:54) > at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:85) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:111) > at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:58) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111) > at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:487) > at org.eclipse.core.databinding.ValueBinding$3$1.run(ValueBinding.java:206) > at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154) > at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172) > at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:196) > at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154) > at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172) > at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:158) > at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:147) > at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46) > at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63) > at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72) > at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63) > at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) > at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69) > at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154) > at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65) > at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65) > at org.eclipse.jface.internal.databinding.viewers.SelectionChangedListener.selectionChanged(SelectionChangedListener.java:36) > at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:244) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:46) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizardModel.setLabels(NewApplicationWizardModel.java:167) > at org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizardModel.setTemplate(NewApplicationWizardModel.java:81) > at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59) > ... 102 more > {code} > It is possible to proceed to wizard, but once it is created, all resources show green mark (everythink is ok), but buildconfig is not created. If I am using this template json directly, from file system (its in repo under examples/jenkins/application-template.json), then the buildconfig is created. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20169) NullPointerException in ReverseEngineeringStrategyUtil#simplePluralize

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20169?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20169: ---------------------------------- Component/s: upstream > NullPointerException in ReverseEngineeringStrategyUtil#simplePluralize > ---------------------------------------------------------------------- > > Key: JBIDE-20169 > URL: https://issues.jboss.org/browse/JBIDE-20169 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > > For strings with length == 1 ReverseEngineeringStrategyUtil#simplePluralize throws NullPointerException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-455) Add fabric8 feature to the EM features. XML.

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-455: -------------------------------- Summary: Add fabric8 feature to the EM features. XML. Key: JBTIS-455 URL: https://issues.jboss.org/browse/JBTIS-455 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.2.GA Reporter: Paul Leacu Assignee: Paul Leacu The fabric8 feature is missing from the EM feature XML. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20169) NullPointerException in ReverseEngineeringStrategyUtil#simplePluralize

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20169: ------------------------------------- Summary: NullPointerException in ReverseEngineeringStrategyUtil#simplePluralize Key: JBIDE-20169 URL: https://issues.jboss.org/browse/JBIDE-20169 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.3.0.Beta1 Reporter: Denis Golovin For strings with length == 1 ReverseEngineeringStrategyUtil#simplePluralize throws NullPointerException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19885) Make target deployment destination configurable

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19885?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19885: ---------------------------------------- Satisfied, closing ;) > Make target deployment destination configurable > ----------------------------------------------- > > Key: JBIDE-19885 > URL: https://issues.jboss.org/browse/JBIDE-19885 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > Now that deploy steps are in the pom files (JBIDE-18772), it would be interesting to make them parameterized so that we could set up a parallel deployment area for JBoss Tools without pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015