May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22454: ----------------------------------- Assignee: Jeff Cantrill > Application Wizard: Build configuration wizard page has redundant environment variables table > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22454 > URL: https://issues.jboss.org/browse/JBIDE-22454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Attachments: screenshot-1.png > > > In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-22454: ---------------------------------- Attachment: screenshot-1.png > Application Wizard: Build configuration wizard page has redundant environment variables table > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22454 > URL: https://issues.jboss.org/browse/JBIDE-22454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Attachments: screenshot-1.png > > > In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22455) When an image for a template cannot be found, Eclipse provides a default one

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22455: ---------------------------------- Summary: When an image for a template cannot be found, Eclipse provides a default one Key: JBIDE-22455 URL: https://issues.jboss.org/browse/JBIDE-22455 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha2 Reporter: Jeff MAURY Fix For: 4.4.x When a template is displayed in the new application wizard and selected, the UI will display an image based on metadata. The URL is computed from the metadata but if there is no corresponding image file, Eclipse will provide a default red squared image that we need to replace by a more Openshift oriented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22197) Icon in template Details of Local Template is not loaded for some templates file

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22197?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22197: ------------------------------------- PR was merged, that adds the java image. We'll still need to better support the case of missing images, that should load a default one. > Icon in template Details of Local Template is not loaded for some templates file > -------------------------------------------------------------------------------- > > Key: JBIDE-22197 > URL: https://issues.jboss.org/browse/JBIDE-22197 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.0.Alpha3 > > Attachments: quickstart-template.json, screenshot-1.png > > > {noformat} > java.io.FileNotFoundException: /icons/apps/java.png > at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:37) > at org.eclipse.osgi.storage.url.BundleResourceHandler.openConnection(BundleResourceHandler.java:169) > at java.net.URL.openConnection(Unknown Source) > at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:32) > at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207) > at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:219) > at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:283) > at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:164) > at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52) > at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:86) > at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192) > at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:214) > at org.jboss.tools.openshift.internal.common.ui.ImageRepository.getImage(ImageRepository.java:85) > at org.jboss.tools.openshift.internal.ui.OpenShiftImages.getAppImage(OpenShiftImages.java:62) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.updateImage(TemplateDetailViews.java:106) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.onVisible(TemplateDetailViews.java:102) > at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:90) > at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:79) > at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews$1.handleValueChange(AbstractStackedDetailViews.java:73) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22434) Properties not showing whole Docker image ID

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22434?page=com.atlassian.jira.plugi... ] Roland Grunberg commented on JBIDE-22434: ----------------------------------------- Yup, I can see this as well now. The 1.22 Remote API doesn't really hint at this ( https://docs.docker.com/engine/reference/api/docker_remote_api_v1.22/#lis... ) and continues to use the old format. For the purposes of presenting to users, I think the digest type prefix should be stripped out, just like the cli commands. I'll file a bug on the Eclipse Docker Tooling for this, and link it here. > Properties not showing whole Docker image ID > -------------------------------------------- > > Key: JBIDE-22434 > URL: https://issues.jboss.org/browse/JBIDE-22434 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.0.Alpha2 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160525-0422-B5425 > Build date: 20160525-0422 > Reporter: Josef Kopriva > Attachments: Dockerfile, Docker_Image_ID.png > > > Image ID in properties tab is not complete, but Parent ID is complete. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- [~maxandersen] The user that's granted push permissions is ONLY used in the context of the GitHub Pull Request Builder plugin AFAIK. If not we could create one just for that. It means that even if the user has full push permission, only some Jenkins plugin that would use this user credentials could do bad things. A regular piece of code running in the build doesn't run as this GitHub user and wouldn't be able to do anything with the repositories. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-722) Fix JDG test and revert wrong fix for UDF import

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/JBTIS-722?page=com.atlassian.jira.plugin.... ] Matus Makovy commented on JBTIS-722: ------------------------------------ [~apodhrad] Yes > Fix JDG test and revert wrong fix for UDF import > ------------------------------------------------ > > Key: JBTIS-722 > URL: https://issues.jboss.org/browse/JBTIS-722 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-722) Fix JDG test and revert wrong fix for UDF import

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-722?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-722: ----------------------------------------- [~mmakovy] is this only for the branch 4.3.x? > Fix JDG test and revert wrong fix for UDF import > ------------------------------------------------ > > Key: JBTIS-722 > URL: https://issues.jboss.org/browse/JBTIS-722 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22348) ServerSOAPFaultException in SOAP11Fault.getProtocolException

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22348?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-22348: -------------------------------------- Fix Version/s: LATER > ServerSOAPFaultException in SOAP11Fault.getProtocolException > ------------------------------------------------------------ > > Key: JBIDE-22348 > URL: https://issues.jboss.org/browse/JBIDE-22348 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Brian Fitzpatrick > Fix For: LATER > > > The following problem was reported via the automated error reporting: > Message: No message > {noformat} > com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: java.lang.Exception: Body not found. Please see the server log to find more detail regarding exact cause of the failure. > at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116) > at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:602) > at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:545) > at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:912) > at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:808) > at com.sun.xml.internal.ws.api.server.ThreadLocalContainerResolver$2$1.run(ThreadLocalContainerResolver.java:97) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.jboss.tools.ws.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | Windows | 6.3.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571f8ce2e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22341) IllegalArgumentException below WSDL2JavaCodeGenConfigWidget$6.widgetSelected (thrown in SWT.error)

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22341?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-22341: -------------------------------------- Fix Version/s: LATER > IllegalArgumentException below WSDL2JavaCodeGenConfigWidget$6.widgetSelected (thrown in SWT.error) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-22341 > URL: https://issues.jboss.org/browse/JBIDE-22341 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Brian Fitzpatrick > Fix For: LATER > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.IllegalArgumentException: Argument cannot be null > at org.eclipse.swt.SWT.error(SWT.java:4472) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.SWT.error(SWT.java:4377) > at org.eclipse.swt.widgets.Widget.error(Widget.java:482) > at org.eclipse.swt.widgets.Text.setText(Text.java:2285) > at org.jboss.tools.ws.creation.ui.widgets.WSDL2JavaCodeGenConfigWidget$6.widgetSelected(WSDL2JavaCodeGenConfigWidget.java:178) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {noformat} > Bundles: > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.jboss.tools.ws.creation.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | MacOSX | 10.11.4 | 10.11.4 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a3d32e4b0e9dd9c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016