January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23731) Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23731?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23731: ------------------------------------- Summary: Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo (was: Integration tests: move central integration tests to jbosstools/jbosstools-central repo) > Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23731 > URL: https://issues.jboss.org/browse/JBIDE-23731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests > Affects Versions: 4.4.2.Final > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23136: ------------------------------------------ [~jcantrill], sorry didn't get this: {quote}Dmitrii Bocharov I would be interested in understanding if this docker output you were logged into 172.30.115.181:5000/{quote} [~jcantrill] as i described in the previous comment, we have access to docker registry, and we tag and push the image using the internal IP in this case. The question is - -is it OK that we have the additional image appear? Sorry if i didn't understand you right. https://github.com/openshift/origin/issues/12603 is not an origin for this issue. I created https://issues.jboss.org/browse/JBIDE-23771 for it > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23769: ------------------------------------ Could we just turn this "error" into a "warning" in error log? This wouldn't at least trigger aeri (creating false reports) and we would still have stacktrace if needed? > New Application: Do not throw exception in error log when provided template is of wrong kind. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23769 > URL: https://issues.jboss.org/browse/JBIDE-23769 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Priority: Minor > > When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log: > {noformat} > !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472 > !MESSAGE Unhandled exception: Wrong resource kind: Pod > !STACK 0 > org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think it's enough to inform the user in the wizard (this is already happening). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23672) Move org.jboss.tools.maven.reddeer to jbosstools-central/maven/test-framework

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23672?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-23672: ---------------------------------------- Assignee: Pavol Srna (was: Dmitrii Bocharov) > Move org.jboss.tools.maven.reddeer to jbosstools-central/maven/test-framework > ----------------------------------------------------------------------------- > > Key: JBIDE-23672 > URL: https://issues.jboss.org/browse/JBIDE-23672 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, maven > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.3.AM2 > > > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > https://github.com/jbosstools/jbosstools-central/tree/master/maven -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23769 at 1/24/17 5:46 AM: ------------------------------------------------------------------- I general having a stacktrace is always a benefit. But here I fully agree with you, this isnt a proper error, it's a user mistake where he's providing the wrong json file. This being said, it's still important that other cases like file IO errors etc. are still being logged. was (Author: adietish): I general having a stacktrace is always a benefit. But here I fully agree with you, this isnt a proper error, it's a user mistake where he's providing the wrong json file. > New Application: Do not throw exception in error log when provided template is of wrong kind. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23769 > URL: https://issues.jboss.org/browse/JBIDE-23769 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Priority: Minor > > When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log: > {noformat} > !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472 > !MESSAGE Unhandled exception: Wrong resource kind: Pod > !STACK 0 > org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think it's enough to inform the user in the wizard (this is already happening). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23769 at 1/24/17 5:43 AM: ------------------------------------------------------------------- I general having a stacktrace is always a benefit. But here I fully agree with you, this isnt a proper error, it's a user mistake where he's providing the wrong json file. was (Author: adietish): I general having a stacktrace is always a benefit. But here I fully agree with you, this isnt a proper error, this a user error where he's providing the wrong json file. > New Application: Do not throw exception in error log when provided template is of wrong kind. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23769 > URL: https://issues.jboss.org/browse/JBIDE-23769 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Priority: Minor > > When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log: > {noformat} > !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472 > !MESSAGE Unhandled exception: Wrong resource kind: Pod > !STACK 0 > org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think it's enough to inform the user in the wizard (this is already happening). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23769: ------------------------------------------ I general having a stacktrace is always a benefit. But here I fully agree with you, this isnt a proper error, this a user error where he's providing the wrong json file. > New Application: Do not throw exception in error log when provided template is of wrong kind. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23769 > URL: https://issues.jboss.org/browse/JBIDE-23769 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Priority: Minor > > When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log: > {noformat} > !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472 > !MESSAGE Unhandled exception: Wrong resource kind: Pod > !STACK 0 > org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think it's enough to inform the user in the wizard (this is already happening). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1023) Features and plugins for Fuse tooling have various versions

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1023?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1023: ------------------------------------------ This is probably caused by FUSETOOLS-2260 > Features and plugins for Fuse tooling have various versions > ----------------------------------------------------------- > > Key: JBTIS-1023 > URL: https://issues.jboss.org/browse/JBTIS-1023 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: build, distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Priority: Blocker > > |org.fusesource.ide.camel.editor.feature|9.1.0.CR1-v20170120-1811-B91| > |org.fusesource.ide.core.feature|9.1.0.CR1-v20170120-1811-B91| > |org.fusesource.ide.jmx.feature|9.1.0.CR1-v20170103-1319-B91| > |org.fusesource.ide.server.extensions.feature|9.1.0.CR1-v20170105-1331-B91| -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1023) Features and plugins for Fuse tooling have various versions

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1023: ---------------------------------------- Summary: Features and plugins for Fuse tooling have various versions Key: JBTIS-1023 URL: https://issues.jboss.org/browse/JBTIS-1023 Project: JBoss Tools Integration Stack Issue Type: Bug Components: build, distribution Affects Versions: 10.1.0.CR1 Reporter: Andrej Podhradsky Priority: Blocker |org.fusesource.ide.camel.editor.feature|9.1.0.CR1-v20170120-1811-B91| |org.fusesource.ide.core.feature|9.1.0.CR1-v20170120-1811-B91| |org.fusesource.ide.jmx.feature|9.1.0.CR1-v20170103-1319-B91| |org.fusesource.ide.server.extensions.feature|9.1.0.CR1-v20170105-1331-B91| -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23774) Update Hibernate Tools dependency to 5.0.4.Final

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23774?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23774: ------------------------------ Fix Version/s: 4.4.3.AM2 > Update Hibernate Tools dependency to 5.0.4.Final > ------------------------------------------------ > > Key: JBIDE-23774 > URL: https://issues.jboss.org/browse/JBIDE-23774 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.3.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017