July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4779) Server adapter: should be able to freely set a war name [JBIDE-26694]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4779?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4779: ----------------------------- Fix Version/s: 12.x > Server adapter: should be able to freely set a war name [JBIDE-26694] > --------------------------------------------------------------------- > > Key: JBDS-4779 > URL: https://issues.jboss.org/browse/JBDS-4779 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio, as used with OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.x > > > The user does not have a choice in naming of deployment artifacts. See verbose description in community tracker JBIDE-26694. > [1] https://issues.jboss.org/browse/JBIDE-26694 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26678) Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26678?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26678: ------------------------------- Affects Version/s: 4.12.0.AM1 > Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy > ------------------------------------------------------------------------------- > > Key: JBIDE-26678 > URL: https://issues.jboss.org/browse/JBIDE-26678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5, CodeReady Studio Version: 12.12.0.AM1, java 8 > Reporter: Zbyněk Červinka > Priority: Major > Fix For: 4.13.x > > Attachments: pe.png, terminal.png > > > Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy, which is misleading and causes problems when accessing the items via RedDeer Project Explorer classes > - after creating new CDI web project in the RH CodeReady Studio and after creating several packages in the project, the Project Explorer shows incorrect tree hierarchy according to: > * how it should be (according to common sense) > * how it is displayed when working with simple *Java project* in RH CodeReady Studio/Eclipse (after creating several packages) > * project files hierarchy stored on the disk (see the *terminal.png* image in the attachment listing the content of the *src* folder on the disk) > - look at the *pe.png* image in the attachment to see that firstly created packed placed in the *src* folder, other packages on the same level as *src* folder -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26678) Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26678?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26678: ------------------------------- Fix Version/s: 4.13.x > Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy > ------------------------------------------------------------------------------- > > Key: JBIDE-26678 > URL: https://issues.jboss.org/browse/JBIDE-26678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5, CodeReady Studio Version: 12.12.0.AM1, java 8 > Reporter: Zbyněk Červinka > Priority: Major > Fix For: 4.13.x > > Attachments: pe.png, terminal.png > > > Project Explorer in RH CodeReady Studio shows incorrect project items hierarchy, which is misleading and causes problems when accessing the items via RedDeer Project Explorer classes > - after creating new CDI web project in the RH CodeReady Studio and after creating several packages in the project, the Project Explorer shows incorrect tree hierarchy according to: > * how it should be (according to common sense) > * how it is displayed when working with simple *Java project* in RH CodeReady Studio/Eclipse (after creating several packages) > * project files hierarchy stored on the disk (see the *terminal.png* image in the attachment listing the content of the *src* folder on the disk) > - look at the *pe.png* image in the attachment to see that firstly created packed placed in the *src* folder, other packages on the same level as *src* folder -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26733) 'Launcher Application' link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio)

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26733?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26733: ------------------------------------ Summary: 'Launcher Application' link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio) (was: Launcher Application link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio)) > 'Launcher Application' link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio) > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26733 > URL: https://issues.jboss.org/browse/JBIDE-26733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.AM1 > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Attachments: Red Hat Central.png, Search.png > > > See the "Red Hat Central.png" image in the attachment (the image shows missing "Launcher Application" link). > The "Launcher Application" is also missing from the search (Search.png image in the attachment). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26733) Launcher Application link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio)

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26733: --------------------------------------- Summary: Launcher Application link is not present in the Red Hat Central and is also missing in the search (in Red Hat CodeReady Studio) Key: JBIDE-26733 URL: https://issues.jboss.org/browse/JBIDE-26733 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.12.0.AM1 Environment: OS X 10.14.5 Reporter: Zbyněk Červinka Assignee: Jeff MAURY Attachments: Red Hat Central.png, Search.png See the "Red Hat Central.png" image in the attachment (the image shows missing "Launcher Application" link). The "Launcher Application" is also missing from the search (Search.png image in the attachment). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26713) Installation of JBT 4.12.0.Final from Update Site Cannot Complete as Requested

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26713?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-26713: ----------------------------------- I have always installed them from that URL since eternity. The main reason being that there is also a URL for installing the tests I guess. In any case if we publish an installation link then IMO either it should work or we shouldn't publish it at all. > Installation of JBT 4.12.0.Final from Update Site Cannot Complete as Requested > ------------------------------------------------------------------------------ > > Key: JBIDE-26713 > URL: https://issues.jboss.org/browse/JBIDE-26713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.12.0.Final > Reporter: Koen Aers > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.13.x > > Attachments: JBIDE-26568.mov > > > While installing JBT from the update site at http://download.jboss.org/jbosstools/photon/staging/updates/core/4.12.0.F... in a fresh Eclipse JEE installation the installation does not finish as requested. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-24498 at 7/8/19 8:23 AM: ------------------------------------------------------------------ [~mgreenbe] Ok for the change in the 1st line, I'd rather keep it short and use "access" then. Actually the docker image is not accessible (you told it to use docker image from docker hub which isnt available), that's why the stream isn't either. If the image is available the stream is available too. The pod, that's supposed to run the docker image then also fails to be created (ImagePullBackOff). You can see this once you closed the dialog and watch the pod in the OpenShift explorer: !pod-deploy-failed.png! In this sense deployment fails. What am I missing? was (Author: adietish): [~mgreenbe] Ok for the change in the 1st line, I'd rather keep in short and use "access" then. Actually the docker image is not accessible (you told it to use docker image from docker hub which isnt available), that's why the stream isn't either. If the image is available the stream is available too. The pod, that's supposed to run the docker image then also fails to be created (ImagePullBackOff). You can see this once you closed the dialog and watch the pod in the OpenShift explorer: !pod-deploy-failed.png! In this sense deployment fails. What am I missing? > Deploy Docker Image wizard: results dialog is not very informative > ------------------------------------------------------------------ > > Key: JBIDE-24498 > URL: https://issues.jboss.org/browse/JBIDE-24498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.13.0.AM1 > > Attachments: image-2017-05-23-11-07-21-461.png, pod-deploy-failed.png, pod-deploy-failed.png, resource-summary-dialog.png > > > steps to reproduce: > # ASSERT: have a docker connection > # ASSERT: have an OpenShift connection > # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..." > # ASSERT: deploy docker image wizard pops up > # EXEC: provide settings and finish the wizard > Result: > A dialog pops up informing you about the result of your deployment. > !image-2017-05-23-11-07-21-461.png! > But the dialog is not very informative, it's far from obvious what the different informations are all about: > * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator) > * There's a list of items. Nothing in the dialog tells the user what these items are. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26732) WildFly example 'jaxws-addressing' contains errors after import

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26732: --------------------------------------- Summary: WildFly example 'jaxws-addressing' contains errors after import Key: JBIDE-26732 URL: https://issues.jboss.org/browse/JBIDE-26732 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.12.0.AM1 Environment: OS X 10.14.5 Reporter: Zbyněk Červinka h2. List of problems: * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 pom.xml /jaxws-addressing-client line 19 Maven Dependency Problem * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1 pom.xml /jaxws-addressing-client line 19 Maven Dependency Problem * Missing artifact xerces:xercesImpl:jar:2.12.0.SP02 pom.xml /jaxws-addressing-client line 19 Maven Dependency Problem * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/org/slf4j/slf4j-api/1.7.22.jbossorg-1/slf4j-api-1.7.22.jbossorg-1.jar' jaxws-addressing-client Build path Build Path Problem * The project cannot be built until build path errors are resolved jaxws-addressing-client Unknown Java Problem -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26731) WildFly example 'jaxws-ejb' contains errors after import

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26731: --------------------------------------- Summary: WildFly example 'jaxws-ejb' contains errors after import Key: JBIDE-26731 URL: https://issues.jboss.org/browse/JBIDE-26731 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.12.0.AM1 Environment: OS X 10.14.5 Reporter: Zbyněk Červinka h2. List of problems: * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 pom.xml /jaxws-ejb-client line 18 Maven Dependency Problem * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1 pom.xml /jaxws-ejb-client line 18 Maven Dependency Problem * Missing artifact xerces:xercesImpl:jar:2.12.0.SP02 pom.xml /jaxws-ejb-client line 18 Maven Dependency Problem * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/org/slf4j/slf4j-api/1.7.22.jbossorg-1/slf4j-api-1.7.22.jbossorg-1.jar' jaxws-ejb-client Build path Build Path Problem * The project cannot be built until build path errors are resolved jaxws-ejb-client Unknown Java Problem -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26730) WildFly example 'jaxws-pojo' contains errors after import

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26730: --------------------------------------- Summary: WildFly example 'jaxws-pojo' contains errors after import Key: JBIDE-26730 URL: https://issues.jboss.org/browse/JBIDE-26730 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Environment: OS X 10.14.5 Reporter: Zbyněk Červinka h2. List of problems: * Missing artifact com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.16-jbossorg-1 pom.xml /jaxws-pojo-client line 19 Maven Dependency Problem * Missing artifact org.slf4j:slf4j-api:jar:1.7.22.jbossorg-1 pom.xml /jaxws-pojo-client line 19 Maven Dependency Problem * Missing artifact xerces:xercesImpl:jar:2.12.0.SP02 pom.xml /jaxws-pojo-client line 19 Maven Dependency Problem * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/org/slf4j/slf4j-api/1.7.22.jbossorg-1/slf4j-api-1.7.22.jbossorg-1.jar' jaxws-pojo-client Build path Build Path Problem * The project cannot be built until build path errors are resolved jaxws-pojo-client Unknown Java Problem -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 July 2019