September 2015 - jbosstools-issues

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20758?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20758: ----------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > 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-20758) NullPointerException when creating new artifact from Properties view

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20758?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20758: ----------------------------------- Fix Version/s: 4.3.0.CR2 (was: 4.3.1.Final) > 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, 4.4.0.Alpha1 > > > 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-20815) For JBIDE 4.3.0.Final: Code Freeze + Branch [Playground]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20815?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20815: -------------------------------------- Assignee: Mickael Istria > For JBIDE 4.3.0.Final: Code Freeze + Branch [Playground] > -------------------------------------------------------- > > Key: JBIDE-20815 > URL: https://issues.jboss.org/browse/JBIDE-20815 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Playground]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground 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-20805) For JBIDE 4.3.0.Final: Code Freeze + Branch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20805?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20805: -------------------------------------- Assignee: Nick Boldt > For JBIDE 4.3.0.Final: Code Freeze + Branch > ------------------------------------------- > > Key: JBIDE-20805 > URL: https://issues.jboss.org/browse/JBIDE-20805 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3530 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20824) For JBIDE 4.3.0.Final: Code Freeze + Branch [Central]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20824?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20824. ---------------------------------- Assignee: Fred Bricon Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Central] > ----------------------------------------------------- > > Key: JBIDE-20824 > URL: https://issues.jboss.org/browse/JBIDE-20824 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Central]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central 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-20810) For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20810?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20810: -------------------------------------- Assignee: Mickael Istria > For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20810 > URL: https://issues.jboss.org/browse/JBIDE-20810 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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-20814) For JBIDE 4.3.0.Final: Code Freeze + Branch [OpenShift]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20814?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20814. ---------------------------------- Assignee: Fred Bricon Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [OpenShift] > ------------------------------------------------------- > > Key: JBIDE-20814 > URL: https://issues.jboss.org/browse/JBIDE-20814 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [OpenShift]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift 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-20811) For JBIDE 4.3.0.Final: Code Freeze + Branch [Server]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20811?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20811. ---------------------------------- Assignee: Rob Stryker Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Server] > ---------------------------------------------------- > > Key: JBIDE-20811 > URL: https://issues.jboss.org/browse/JBIDE-20811 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Server]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server 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-20806) For JBIDE 4.3.0.Final: Code Freeze + Branch [Aerogear]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20806?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20806. ---------------------------------- Assignee: Gorkem Ercan Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [Aerogear] > ------------------------------------------------------ > > Key: JBIDE-20806 > URL: https://issues.jboss.org/browse/JBIDE-20806 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Aerogear]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear 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] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-508: ----------------------------- Description: While reviewing JBIDE-20803 I noticed the following: {code} jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. was: While reviewing JBIDE-20803 I noticed the following: {code} jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... {code} The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: But there are a few problems: 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. #1 is mainly just to reduce the number of updatesites actually necessary for users to work with #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. I would also have expected that the discovery site with the discoveyr plugins was kept *separate* from the actual updatesites to avoid any coupling between these. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- 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