September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23133) Make sure magic file library is beta1 quality

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23133?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23133: -------------------------------- Fix Version/s: 4.4.2.AM1 > Make sure magic file library is beta1 quality > ---------------------------------------------- > > Key: JBIDE-23133 > URL: https://issues.jboss.org/browse/JBIDE-23133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > The foundation.ui dependency on magic file should be beta1. This also means a beta1 build must be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23133) Make sure magic file library is beta1 quality

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23133?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23133: -------------------------------- Sprint: devex #120 September 2016 > Make sure magic file library is beta1 quality > ---------------------------------------------- > > Key: JBIDE-23133 > URL: https://issues.jboss.org/browse/JBIDE-23133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > The foundation.ui dependency on magic file should be beta1. This also means a beta1 build must be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23133) Make sure magic file library is beta1 quality

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23133: ----------------------------------- Summary: Make sure magic file library is beta1 quality Key: JBIDE-23133 URL: https://issues.jboss.org/browse/JBIDE-23133 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.4.2.AM1 Reporter: Rob Stryker The foundation.ui dependency on magic file should be beta1. This also means a beta1 build must be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23133) Make sure magic file library is beta1 quality

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23133?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23133: ----------------------------------- Assignee: Rob Stryker > Make sure magic file library is beta1 quality > ---------------------------------------------- > > Key: JBIDE-23133 > URL: https://issues.jboss.org/browse/JBIDE-23133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > > The foundation.ui dependency on magic file should be beta1. This also means a beta1 build must be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23035) Support WildFly 10.1 - change server adapter name

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23035?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23035. --------------------------------- > Support WildFly 10.1 - change server adapter name > ------------------------------------------------- > > Key: JBIDE-23035 > URL: https://issues.jboss.org/browse/JBIDE-23035 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.1.Final > > > WildFly 10.1 has been released. > We need to make sure it works properly. > My initial test doesn't show any problems. The server can be added both manually and using runtime detection which properly recognizes the version as 10.1. > AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23129) Figure out mechanism to ensure news in Red Hat Central are always up to date.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23129?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-23129: ------------------------------------- I cooked up a script that calls the tiny rss api to refresh the feeds. I'll set up a Jenkins job to kick it once a day, hoping that'll fix the issue once and for all > Figure out mechanism to ensure news in Red Hat Central are always up to date. > ----------------------------------------------------------------------------- > > Key: JBIDE-23129 > URL: https://issues.jboss.org/browse/JBIDE-23129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.Final > Reporter: Radim Hopp > Assignee: Fred Bricon > > According to Fred's comment in JBIDE-23053, some manual work is needed for Central (feedburner) to pick up latest news. We've already had cases when news in Red Hat Central weren't up to date, because nobody did this manual refresh. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23129) Figure out mechanism to ensure news in Red Hat Central are always up to date.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23129?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-23129: ----------------------------------- Assignee: Fred Bricon > Figure out mechanism to ensure news in Red Hat Central are always up to date. > ----------------------------------------------------------------------------- > > Key: JBIDE-23129 > URL: https://issues.jboss.org/browse/JBIDE-23129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.Final > Reporter: Radim Hopp > Assignee: Fred Bricon > > According to Fred's comment in JBIDE-23053, some manual work is needed for Central (feedburner) to pick up latest news. We've already had cases when news in Red Hat Central weren't up to date, because nobody did this manual refresh. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23035) Support WildFly 10.1 - change server adapter name

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23035?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23035. --------------------------------- Resolution: Done > Support WildFly 10.1 - change server adapter name > ------------------------------------------------- > > Key: JBIDE-23035 > URL: https://issues.jboss.org/browse/JBIDE-23035 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.1.Final > > > WildFly 10.1 has been released. > We need to make sure it works properly. > My initial test doesn't show any problems. The server can be added both manually and using runtime detection which properly recognizes the version as 10.1. > AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22580) Deploy Docker Image wizard: Cannot push already tagged image to docker registry

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22580: ---------------------------------- Release Notes Text: (was: Yeah, this is resolved. Resolving as done. Verified in DevStudio 10.1.0.GA Build id: GA-v20160902-1725-B43) > Deploy Docker Image wizard: Cannot push already tagged image to docker registry > ------------------------------------------------------------------------------- > > Key: JBIDE-22580 > URL: https://issues.jboss.org/browse/JBIDE-22580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.1.Final > > > There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace > {code}Failed to push the selected Docker image into OpenShift registry > org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22580) Deploy Docker Image wizard: Cannot push already tagged image to docker registry

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22580: --------------------------------------- Yeah, this is resolved. Resolving as done. Verified in DevStudio 10.1.0.GA Build id: GA-v20160902-1725-B43 > Deploy Docker Image wizard: Cannot push already tagged image to docker registry > ------------------------------------------------------------------------------- > > Key: JBIDE-22580 > URL: https://issues.jboss.org/browse/JBIDE-22580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.1.Final > > > There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace > {code}Failed to push the selected Docker image into OpenShift registry > org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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