May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19756: ---------------------------------- Assignee: Nick Boldt > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19760: ------------------------------------- Summary: Add route support to OpenShift explorer Key: JBIDE-19760 URL: https://issues.jboss.org/browse/JBIDE-19760 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Add support for viewing routes in OpenShiftExplorer and property pane -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19756: ------------------------------- Fix Version/s: 4.3.0.Beta1 > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19756: ------------------------------- Affects Version/s: 4.3.0.Beta1 > jbosstools-src.zip has incomplete/misleading version info in folder names/structure > ----------------------------------------------------------------------------------- > > Key: JBIDE-19756 > URL: https://issues.jboss.org/browse/JBIDE-19756 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named: > <componentname>_<buildqualifier>_<sha1> > example: > jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad > A few issues with this: > a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ? > b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19008: ---------------------------------- Description: We should allow users to remove OpenShift v3 resources. Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up. Any resource in the browser may be deleted except projects. Project are a special case where we MAY need to 'cleanup' all the resources associated with the project. Defer handling that case for now was: We should allow users to remove OpenShift v3 resources. Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up > As a user, I want to delete OpenShift resources > ----------------------------------------------- > > Key: JBIDE-19008 > URL: https://issues.jboss.org/browse/JBIDE-19008 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > We should allow users to remove OpenShift v3 resources. > Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up. > Any resource in the browser may be deleted except projects. Project are a special case where we MAY need to 'cleanup' all the resources associated with the project. Defer handling that case for now -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19008: ------------------------------------- Assignee: Jeff Cantrill > As a user, I want to delete OpenShift resources > ----------------------------------------------- > > Key: JBIDE-19008 > URL: https://issues.jboss.org/browse/JBIDE-19008 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > We should allow users to remove OpenShift v3 resources. > Beside the primary usecase there's an additional requirement: If you submit several resource creations in 1 config/file the backend might stop processing right in the middle, the operation is not transactional. We therefore need to allow the user to clean up -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19723) Add templates from openshift namespace for 'create from template'

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19723?page=com.atlassian.jira.plugi... ] Jeff Cantrill closed JBIDE-19723. --------------------------------- Resolution: Duplicate Issue duplicate of JBIDE-19736 > Add templates from openshift namespace for 'create from template' > ----------------------------------------------------------------- > > Key: JBIDE-19723 > URL: https://issues.jboss.org/browse/JBIDE-19723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > > When getting templates for your project to create a new application, also get the templates from the 'openshift' namespace -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19748) No error or message is displayed when a project namespace has no templates

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19748?page=com.atlassian.jira.plugi... ] Jeff Cantrill closed JBIDE-19748. --------------------------------- Resolution: Done Not an issue > No error or message is displayed when a project namespace has no templates > -------------------------------------------------------------------------- > > Key: JBIDE-19748 > URL: https://issues.jboss.org/browse/JBIDE-19748 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > The following error when no templates are in a project namespace: > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) > at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:583) > at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1001) > at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700) > at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1349) > at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353) > at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906) > at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617) > at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:815) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791) > at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541) > at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790) > at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462) > at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423) > at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517) > at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292) > at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701) > at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.createTemplatesViewer(ResourcesDetailsPage.java:66) > at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.doCreateControls(ResourcesDetailsPage.java:48) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597) > at org.eclipse.jface.window.Window.create(Window.java:430) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.createWizardDialog(WizardUtils.java:53) > at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:74) > at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:67) > at org.jboss.tools.openshift.internal.ui.command.NewApplicationHandler.execute(NewApplicationHandler.java:36) > 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.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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > ... 38 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19637: ------------------------------------- I confirm [~snjeza] is *very* good at discovering root causes of weird bugs. PR fixes the issue on my mac \o/ > Runtime download not working from New Server dialog > --------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.3.0.Beta1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19007: --------------------------------------- [~mlabuda] [~adietish] I think I already spoke to [~mlabuda] about this one but: # Add a build config from the command line using 'osc' that has a build trigger # In eclipse, Open the OpenShift explorer view and expand the project to view the buildconfig # In eclipse, Click the buildconfig # Verify in the property pane that the build hook url matches what is returned from running the command 'osc describe buildconfig <buildconfigname> -n <projectname>' > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015