May 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26639) Connect wizard (MacOS): have to repeatedly allow the security certificate of open.paas.redhat.com

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26639?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26639: ------------------------------------- Summary: Connect wizard (MacOS): have to repeatedly allow the security certificate of open.paas.redhat.com (was: Connect wizard: have to repeatedly allow the security certificate of open.paas.redhat.com) Environment: MacOS > Connect wizard (MacOS): have to repeatedly allow the security certificate of open.paas.redhat.com > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-26639 > URL: https://issues.jboss.org/browse/JBIDE-26639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.12.0.AM1 > Environment: MacOS > Reporter: André Dietisheim > Priority: Major > Fix For: 4.12.x > > Attachments: image-2019-05-07-22-56-12-592.png > > > steps: > # EXEC: open new connection wizard > # EXEC: in server use *https://open.paas.redhat.com* > # EXEC: hit *retrieve* link > # ASSERT: dialog shows up where you should accept the self-signed certificate > !image-2019-05-07-22-56-12-592.png! > # EXEC: check *always trust "open.paas.redhat.com"* & hit *Continue* > Result: > The dialog shows up again with the *always trust "open.paas.redhat.com"* unchecked. It doesnt seem to matter if you check it: the dialog shows up again and again and again and again... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26639) Connect wizard: have to repeatedly allow the security certificate of open.paas.redhat.com

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26639?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26639: ---------------------------------- Summary: Connect wizard: have to repeatedly allow the security certificate of open.paas.redhat.com (was: Connect wizard: have to repeatedly allow the security certificate of open.paas.redha.com) > Connect wizard: have to repeatedly allow the security certificate of open.paas.redhat.com > ----------------------------------------------------------------------------------------- > > Key: JBIDE-26639 > URL: https://issues.jboss.org/browse/JBIDE-26639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.12.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.12.x > > Attachments: image-2019-05-07-22-56-12-592.png > > > steps: > # EXEC: open new connection wizard > # EXEC: in server use *https://open.paas.redhat.com* > # EXEC: hit *retrieve* link > # ASSERT: dialog shows up where you should accept the self-signed certificate > !image-2019-05-07-22-56-12-592.png! > # EXEC: check *always trust "open.paas.redhat.com"* & hit *Continue* > Result: > The dialog shows up again with the *always trust "open.paas.redhat.com"* unchecked. It doesnt seem to matter if you check it: the dialog shows up again and again and again and again... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26640) "Enterprise Application Project" project maven build is failing (after conversion to maven project)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26640?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26640: ------------------------------- Fix Version/s: 4.12.0.AM1 > "Enterprise Application Project" project maven build is failing (after conversion to maven project) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26640 > URL: https://issues.jboss.org/browse/JBIDE-26640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.11.0.Final > Environment: OS X 10.14.4 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > "Enterprise Application Project" project maven build after conversion to maven project is failing - it looks like the project cant see the modules' pom.xml: > [ERROR] Failed to execute goal on project ear: Could not resolve dependencies for project ear:ear:ear:0.0.1-SNAPSHOT: The following artifacts could not be resolved: earClient:earClient:jar:0.0.1-SNAPSHOT, earEJB:earEJB:jar:0.0.1-SNAPSHOT, earConnector:earConnector:rar:0.0.1-SNAPSHOT, earWeb:earWeb:war:0.0.1-SNAPSHOT: Could not find artifact earClient:earClient:jar:0.0.1-SNAPSHOT -> [Help 1] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4773) Newest Eclipse 2019-06 M1 build offers older JBT/Studio (4.9.0/12.9.0) in Marketplace

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4773?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4773: ----------------------------- Fix Version/s: 12.12.0.GA > Newest Eclipse 2019-06 M1 build offers older JBT/Studio (4.9.0/12.9.0) in Marketplace > ------------------------------------------------------------------------------------- > > Key: JBDS-4773 > URL: https://issues.jboss.org/browse/JBDS-4773 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: marketplace > Affects Versions: 12.12.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.12.0.GA > > Attachments: Screenshot_20190429_093317.png, Screenshot_20190429_140432.png, screenshot-1.png > > > Development build of Eclipse (2019-06) offers only older JBT/RH CR studio in version 4.9/12.9 in marketplace while 2019-03 eclipse shows proper 4.11/12.11 GA version of software. I believe that there is missing some configuration in our update sites for marketplace. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26640) "Enterprise Application Project" project maven build is failing (after conversion to maven project)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26640?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26640: ------------------------------- Component/s: maven > "Enterprise Application Project" project maven build is failing (after conversion to maven project) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26640 > URL: https://issues.jboss.org/browse/JBIDE-26640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.11.0.Final > Environment: OS X 10.14.4 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > "Enterprise Application Project" project maven build after conversion to maven project is failing - it looks like the project cant see the modules' pom.xml: > [ERROR] Failed to execute goal on project ear: Could not resolve dependencies for project ear:ear:ear:0.0.1-SNAPSHOT: The following artifacts could not be resolved: earClient:earClient:jar:0.0.1-SNAPSHOT, earEJB:earEJB:jar:0.0.1-SNAPSHOT, earConnector:earConnector:rar:0.0.1-SNAPSHOT, earWeb:earWeb:war:0.0.1-SNAPSHOT: Could not find artifact earClient:earClient:jar:0.0.1-SNAPSHOT -> [Help 1] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26160: ------------------------------------- Fix Version/s: 4.12.0.AM1 (was: 4.12.0.Final) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: André Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: server_adapter > Fix For: 4.12.0.AM1 > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26160: ------------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.0.AM1) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: André Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: server_adapter > Fix For: 4.12.0.Final > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1247) Remove tests for Teiid Designer

by Andrej Podhradsky (Jira)

[ https://issues.jboss.org/browse/JBTIS-1247?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1247. ------------------------------------ Resolution: Done > Remove tests for Teiid Designer > ------------------------------- > > Key: JBTIS-1247 > URL: https://issues.jboss.org/browse/JBTIS-1247 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.11.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Priority: Major > Fix For: 4.11.0.Final > > > Please remove tests related to Teiid Designer. The Teiid Designer is not supported for JBT 4.11.0 - it is supported only on JBT 4.6.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26640) "Enterprise Application Project" project maven build after conversion to maven project is failing

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26640: --------------------------------------- Summary: "Enterprise Application Project" project maven build after conversion to maven project is failing Key: JBIDE-26640 URL: https://issues.jboss.org/browse/JBIDE-26640 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.11.0.Final Environment: OS X 10.14.4 Reporter: Zbyněk Červinka Assignee: Jeff MAURY "Enterprise Application Project" project maven build after conversion to maven project is failing - it looks like the project cant see the modules' pom.xml: [ERROR] Failed to execute goal on project ear: Could not resolve dependencies for project ear:ear:ear:0.0.1-SNAPSHOT: The following artifacts could not be resolved: earClient:earClient:jar:0.0.1-SNAPSHOT, earEJB:earEJB:jar:0.0.1-SNAPSHOT, earConnector:earConnector:rar:0.0.1-SNAPSHOT, earWeb:earWeb:war:0.0.1-SNAPSHOT: Could not find artifact earClient:earClient:jar:0.0.1-SNAPSHOT -> [Help 1] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26640) "Enterprise Application Project" project maven build after conversion to maven project is failing

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26640?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26640: ------------------------------------ Steps to Reproduce: 1) create new "Enterprise Application Project" project - fill in Project name and click next - click on "New Module..." button and make sure all 4 default modules are checked to be created - click Finish 2) In package Explorer -> right click on each modul and project itself -> Configure -> Convert to maven project -> Finish 3) Build all 4 modules - Client, Connector, EJB, web (build should be successful) - right click on module -> Run As -> Maven build... -> insert "clean install" into "Goals:" input and click "Run" 4) Build the whole project (same steps as building modules) -> fail was: 1) create new "Enterprise Application Project" project - fill in Project name and click next - click on "New Module..." button and make sure all 4 default modules are checked to be created - click Finish 2) In package Explorer -> right click on each modul and project itself -> Configure -> Convert to maven project -> Finish 3) Build all 4 modules - Client, Connector, EJB, web (build should be successful) - right click on module -> Run As -> Maven build... -> insert "clean install" into "Goals:" input and click "Run" 4) Build the whole project (same steps as building modules) -> fail > "Enterprise Application Project" project maven build after conversion to maven project is failing > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-26640 > URL: https://issues.jboss.org/browse/JBIDE-26640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.11.0.Final > Environment: OS X 10.14.4 > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > "Enterprise Application Project" project maven build after conversion to maven project is failing - it looks like the project cant see the modules' pom.xml: > [ERROR] Failed to execute goal on project ear: Could not resolve dependencies for project ear:ear:ear:0.0.1-SNAPSHOT: The following artifacts could not be resolved: earClient:earClient:jar:0.0.1-SNAPSHOT, earEJB:earEJB:jar:0.0.1-SNAPSHOT, earConnector:earConnector:rar:0.0.1-SNAPSHOT, earWeb:earWeb:war:0.0.1-SNAPSHOT: Could not find artifact earClient:earClient:jar:0.0.1-SNAPSHOT -> [Help 1] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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 2019