September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22446. --------------------------------- Verified once more in master. > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20362. --------------------------------- Verified once more in devstudio-10.1.0.GA-v20160902-1725-B43-installer-eap.jar > Extracting of a download runtime is slow on Mac > ----------------------------------------------- > > Key: JBIDE-20362 > URL: https://issues.jboss.org/browse/JBIDE-20362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > While playing with the Download runtime fuctionality, I noticed that once a runtime (e.g. EAP 6.2) is downloaded, the extraction takes very long. I think it used to be fast and the extraction was done without any progress reporting. But now it seems that every subdirectory in the archive is being printed out which slows it down. > This extraction process took 1 min 23 sec for EAP 6.2 and I have an SSD. On a command line, this would take a few seconds. > I think the solution may be to simply show "Extracting" without printing out each file/directory that is being extracted. > (Furthermore, the progress bar does not reflect the progress - it seems there is still only perhaps 5 % done and then it's suddenly over.) > I can record a screencast if you like, but I think this should be easy to replicate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4045) Createnewandnoteworthy.py are not mentioned in project readme

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4045?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4045: ------------------------------- Affects Version/s: 10.1.0.GA (was: 4.4) > Createnewandnoteworthy.py are not mentioned in project readme > ------------------------------------------------------------- > > Key: JBDS-4045 > URL: https://issues.jboss.org/browse/JBDS-4045 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > > The script *createnewandnoteworthy.py* has been copied to *jbosstools-build-ci* project on Git Hub ([JBIDE-23012|https://issues.jboss.org/browse/JBIDE-23012]), but isn't mentioned in readme file as another scripts. Please add same descripton to [readme.adoc|https://github.com/jbosstools/jbosstools-build-ci/blob/jbosst...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22782) Create integration tests PR check job for central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22782?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22782. ------------------------------ Resolution: Done Done. > Create integration tests PR check job for central > ------------------------------------------------- > > Key: JBIDE-22782 > URL: https://issues.jboss.org/browse/JBIDE-22782 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Radim Hopp > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22798) Create integration tests PR check job for runtime-detection

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22798?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22798. ------------------------------ Resolution: Done Done. > Create integration tests PR check job for runtime-detection > ----------------------------------------------------------- > > Key: JBIDE-22798 > URL: https://issues.jboss.org/browse/JBIDE-22798 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Radim Hopp > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23053) Central news info does not seem uptodate

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23053?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23053. ------------------------------ I'm closing this one (verified in Devstudio 10.1.0.GA) and creating a followup: https://issues.jboss.org/browse/JBIDE-23129 > Central news info does not seem uptodate > ---------------------------------------- > > Key: JBIDE-23053 > URL: https://issues.jboss.org/browse/JBIDE-23053 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM3 > Reporter: Jeff MAURY > Assignee: Fred Bricon > Fix For: 4.4.1.Final > > > The RedHat Central view does not seem to display uptodate news: latest info is from June 2016 which is almost 3 months old -- 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 Radim Hopp (JIRA)

Radim Hopp created JBIDE-23129: ---------------------------------- Summary: 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 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-23043) Not working connection to CDK Docker deamon

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23043. --------------------------------- Docker tooling works after update. Verified in: Version: 10.1.0.GA Build id: GA-v20160902-1725-B43 Build date: 20160902-1725 Docker Tooling from nightly update site: 2.2.0.201609022202 > Not working connection to CDK Docker deamon > ------------------------------------------- > > Key: JBIDE-23043 > URL: https://issues.jboss.org/browse/JBIDE-23043 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, target-platform > Affects Versions: 4.4.1.Final > Environment: F24, > Devstudio: > Version: 10.1.0.GA > Build id: GA-v20160825-0621-B5857 > Build date: 20160825-0621 > Docker Tooling: > 2.1.0.20160825102 > Reporter: Josef Kopriva > Assignee: Jeff Johnston > Priority: Blocker > Fix For: 4.4.1.Final > > Attachments: RC1vs0825N.txt, RC1vs0825N_sorted.txt > > > After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates. > Stacktrace: > {code:java} > An internal error occurred during: "Opening connection...". > java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser > at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80) > at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64) > at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83) > at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4045) Createnewandnoteworthy.py are not mentioned in project readme

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4045?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4045: ------------------------------------- [~nickboldt], this is a follow up of JBIDE-23012 . I didn't quite understand why this JIRA requests the readme to modified for 4.4.x which is a bit old now. But it turns out that you copied that script to 4.4.x (see JBIDE-23012) and not master. Was it a mistake or is there a reason for that? > Createnewandnoteworthy.py are not mentioned in project readme > ------------------------------------------------------------- > > Key: JBDS-4045 > URL: https://issues.jboss.org/browse/JBDS-4045 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 4.4 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > > The script *createnewandnoteworthy.py* has been copied to *jbosstools-build-ci* project on Git Hub ([JBIDE-23012|https://issues.jboss.org/browse/JBIDE-23012]), but isn't mentioned in readme file as another scripts. Please add same descripton to [readme.adoc|https://github.com/jbosstools/jbosstools-build-ci/blob/jbosst...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ] Radim Hopp edited comment on JBIDE-22916 at 9/6/16 6:36 AM: ------------------------------------------------------------ I have to reopen this, because in build 10.1.0.GA-v20160902-1725-B43 this is not working. When the docker image is not in the docker daemon, the metadata are not loaded no matter if I use Search button or paste the image name manually. It only works when the image is pulled (using ImagePull wizard from Docker Explorer) before the Deploy Image to OpenShift wizard is executed. was (Author: rhopp): I have to reopen this, because in build 10.1.0.GA-v20160902-1725-B43 this is not working. When the docker image is not in the docker daemon, the metadata are not loaded no matter if I use Search button or paste the image name manually. It only works when the image is pulled (using ImagePull wizard from Docker Explorer) before the Deploy Image to OpenShift wizard is executed (This was resolved in JBIDE-23094) > Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-22916 > URL: https://issues.jboss.org/browse/JBIDE-22916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.Final > > > When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest". > You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image. -- 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