September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20484) Application wizard: [origin_intservice_51] white space value should not allowed for required parameter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20484?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20484: ------------------------------------- Fix Version/s: (was: 4.3.1.Final) > Application wizard: [origin_intservice_51] white space value should not allowed for required parameter > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20484 > URL: https://issues.jboss.org/browse/JBIDE-20484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150820-0237-B971 > Reporter: Yue Wang > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.x > > > " "(several white spaces) value should not allowed for a required parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20401. --------------------------------- Verified in JBDS 9.0.0.CR1a build ID B105. > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20385) Upgrade FreeMarker to 2.3.23

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20385?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20385: ---------------------------------- Story Points: 1 Sprint: Sprint #9 September 2016 > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20385 > URL: https://issues.jboss.org/browse/JBIDE-20385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20385) Upgrade FreeMarker to 2.3.23

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20385?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20385: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > Upgrade FreeMarker to 2.3.23 > ---------------------------- > > Key: JBIDE-20385 > URL: https://issues.jboss.org/browse/JBIDE-20385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20758) NullPointerException when creating new artifact from Properties view

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20758?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-20758: -------------------------------------- +1 ;-) > NullPointerException when creating new artifact from Properties view > -------------------------------------------------------------------- > > Key: JBIDE-20758 > URL: https://issues.jboss.org/browse/JBIDE-20758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.CR1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.CR2 > > > When I try to create new artifact from suggestion box in Properties view, I get the following NullPointerException. It happens only if the ref field is empty, it does not happen if there is something written. > {code} > java.lang.NullPointerException > at org.jboss.tools.batch.ui.editor.internal.action.OpenOrCreateArtifactActionDelegate.run(OpenOrCreateArtifactActionDelegate.java:139) > at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDialog$1.linkActivated(PropertyEditorAssistDialog.java:146) > at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.activateLink(SapphireFormText.java:1583) > at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.handleMouseClick(SapphireFormText.java:1374) > at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText.access$16(SapphireFormText.java:1345) > at org.eclipse.sapphire.ui.forms.swt.internal.text.SapphireFormText$6.mouseUp(SapphireFormText.java:445) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > 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:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.sapphire.ui.forms.swt.Popup.open(Popup.java:250) > at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator.openAssistDialog(PropertyEditorAssistDecorator.java:407) > at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator.access$3(PropertyEditorAssistDecorator.java:385) > at org.eclipse.sapphire.ui.assist.internal.PropertyEditorAssistDecorator$6.mouseUp(PropertyEditorAssistDecorator.java:285) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220) > 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:1329) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20778) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Integration Tests]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20778?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20778. ---------------------------------- > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Integration Tests] > --------------------------------------------------------------------- > > Key: JBIDE-20778 > URL: https://issues.jboss.org/browse/JBIDE-20778 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Integration Tests]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20709) tools.jboss.org/features: Add OpenShift 3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20709?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-20709 at 9/24/15 7:15 PM: -------------------------------------------------------------- So to be clear, we should display 2 entries like: !http://content.screencast.com/users/fbricon/folders/Jing/media/368e5764-c196-401c-845e-083ef44ce382/00000199.png|width=600! was (Author: fbricon): So to be clear, we should display 2 entries like: !http://content.screencast.com/users/fbricon/folders/Jing/media/4b440895-5f82-42d8-acf8-8d1dcda5c194/00000198.png|width=600! > tools.jboss.org/features: Add OpenShift 3 > ----------------------------------------- > > Key: JBIDE-20709 > URL: https://issues.jboss.org/browse/JBIDE-20709 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > We should add OpenShift 3 to http://tools.jboss.org/features/openshift.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20788) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Birt]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20788?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-20788. --------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Birt] > -------------------------------------------------------- > > Key: JBIDE-20788 > URL: https://issues.jboss.org/browse/JBIDE-20788 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Birt]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20709) tools.jboss.org/features: Add OpenShift 3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20709?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20709: ------------------------------------- So to be clear, we should display 2 entries like: !http://content.screencast.com/users/fbricon/folders/Jing/media/4b440895-5f82-42d8-acf8-8d1dcda5c194/00000198.png|width=600! > tools.jboss.org/features: Add OpenShift 3 > ----------------------------------------- > > Key: JBIDE-20709 > URL: https://issues.jboss.org/browse/JBIDE-20709 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Fix For: 4.3.0.Final > > > We should add OpenShift 3 to http://tools.jboss.org/features/openshift.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20791) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20791?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-20791. --------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Arquillian] > -------------------------------------------------------------- > > Key: JBIDE-20791 > URL: https://issues.jboss.org/browse/JBIDE-20791 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Arquillian]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 September 2015