September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18432) consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18432?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-18432: ---------------------------------------------- Assignee: Konstantin Marmalyukov > consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18432 > URL: https://issues.jboss.org/browse/JBIDE-18432 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Should we consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0, since it's no longer in the VPE project but in the Browsersim project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18431) consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18431?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-18431: ---------------------------------------------- Assignee: Konstantin Marmalyukov > consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0 > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18431 > URL: https://issues.jboss.org/browse/JBIDE-18431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18432) consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18432?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18432: ------------------------------- Component/s: browsersim (was: aerogear-hybrid) > consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18432 > URL: https://issues.jboss.org/browse/JBIDE-18432 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18432) consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18432?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18432: ------------------------------- Description: Should we consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0, since it's no longer in the VPE project but in the Browsersim project? (was: Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project?) > consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18432 > URL: https://issues.jboss.org/browse/JBIDE-18432 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Should we consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0, since it's no longer in the VPE project but in the Browsersim project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18431) consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18431?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-18431: ------------------------------------------- Fix Version/s: 4.3.0.Alpha1 > consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0 > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18431 > URL: https://issues.jboss.org/browse/JBIDE-18431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18432) consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18432: ---------------------------------- Summary: consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0 Key: JBIDE-18432 URL: https://issues.jboss.org/browse/JBIDE-18432 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha1 Reporter: Nick Boldt Priority: Minor Fix For: 4.3.0.Alpha1 Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18431) consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18431: ---------------------------------- Summary: consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0 Key: JBIDE-18431 URL: https://issues.jboss.org/browse/JBIDE-18431 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha1 Reporter: Nick Boldt Priority: Minor Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18414) Forge 'New Project' wizard - 'From Archetype' option broken

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18414?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-18414: ----------------------------------------- This happens because our {{org.jboss.forge.addon.maven.projects.archetype.ArchetypeHelper}} didn't evaluate the #if statements in the resulting pom.xml. Can we move this issue to the FORGE project? > Forge 'New Project' wizard - 'From Archetype' option broken > ----------------------------------------------------------- > > Key: JBIDE-18414 > URL: https://issues.jboss.org/browse/JBIDE-18414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: OS X > Reporter: Michelle Murray > > Forge 2 New Project wizard fails for project type 'From Archetype' > * Ctrl+4 > * New Project > * Project name: blah > * Project type: From Archetype > * Archetype Group Id: org.jboss.aerogear.archetypes > * Archetype Artifact Id: jboss-html5-mobile-archetype > * Archetype Version: 7.1.3.Final > * Archetype Repository: http://repo1.maven.org/maven2/ > or > * Archetype Group Id: org.jboss.archetype.wfk > * Archetype Artifact Id: jboss-html5-mobile-archetype > * Archetype Version: 2.6.0.Final > * Archetype Repository: http://repository.jboss.org/nexus/content/groups/public > Wizard fails with message in Error Log: > {noformat} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.RuntimeException: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ... version of the JBoss EAP components we want to use -->\n <v... @50:11) ) > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:209) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4721) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper.onFinish(ForgeWizardHelper.java:56) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:115) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.lang.RuntimeException: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ... version of the JBoss EAP components we want to use -->\n <v... @50:11) > at org.jboss.forge.addon.maven.resources.MavenModelResourceImpl.initialize(MavenModelResourceImpl.java:120) > at org.jboss.forge.addon.maven.resources.MavenModelResourceImpl.getCurrentModel(MavenModelResourceImpl.java:96) > at org.jboss.forge.addon.maven.projects.MavenFacetImpl.getModel(MavenFacetImpl.java:124) > at sun.reflect.GeneratedMethodAccessor154.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.maven.projects.MavenFacetImpl_$$_javassist_55122075-0c11-493f-a1ca-83e805ea5320.getModel(MavenFacetImpl_$$_javassist_55122075-0c11-493f-a1ca-83e805ea5320.java) > at org.jboss.forge.addon.maven.projects.facets.MavenMetadataFacet.getProjectName(MavenMetadataFacet.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.maven.projects.facets.MavenMetadataFacet_$$_javassist_2cf3fcd2-cfbc-4910-bfb8-de40dd12cabf.getProjectName(MavenMetadataFacet_$$_javassist_2cf3fcd2-cfbc-4910-bfb8-de40dd12cabf.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.facets.Facet_$$_javassist_718e47d0-0ab5-4306-98e5-0a8169186093.getProjectName(Facet_$$_javassist_718e47d0-0ab5-4306-98e5-0a8169186093.java) > at org.jboss.tools.forge.ui.internal.ext.importer.ImportEclipseProjectListener.doImport(ImportEclipseProjectListener.java:48) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper.importNewProjects(ForgeWizardHelper.java:102) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper.access$0(ForgeWizardHelper.java:100) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizardHelper$1.run(ForgeWizardHelper.java:59) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:175) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:390) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059) > at org.jboss.tools.forge.ui.internal.ext.dialog.ForgeCommandDialog.run(ForgeCommandDialog.java:56) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:97) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard.performFinish(ForgeWizard.java:87) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:205) > at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:102) > at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:232) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:322) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:312) > at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:461) > 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:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected START_TAG or END_TAG not TEXT (position: TEXT seen ... version of the JBoss EAP components we want to use -->\n <v... @50:11) > at org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1121) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2178) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3807) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:557) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:571) > at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:600) > at org.jboss.forge.addon.maven.resources.MavenModelResourceImpl.initialize(MavenModelResourceImpl.java:115) > ... 90 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18306: ------------------------------------- Attachment: error-create-obsolete-cartridge.png > The obsoleted cartridges are still shown > ---------------------------------------- > > Key: JBIDE-18306 > URL: https://issues.jboss.org/browse/JBIDE-18306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.2.Final > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: edit-embedded-cartridges.png, error-create-obsolete-cartridge.png > > > The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list. > the issue may due to java-client not using the latest 1.7 version restapi. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18306?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18306: ------------------------------------------ latest OpenShift Online will list obsolete cartridges but wont let you create apps with obsolete cartridges: !error-create-obsolete-cartridge.png! > The obsoleted cartridges are still shown > ---------------------------------------- > > Key: JBIDE-18306 > URL: https://issues.jboss.org/browse/JBIDE-18306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.2.Final > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: edit-embedded-cartridges.png > > > The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list. > the issue may due to java-client not using the latest 1.7 version restapi. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 2014