January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23782) Server adapter: Should keep trying to start (silently) instead of erroring and giving up

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23782?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23782: ------------------------------------- Description: steps to reproduce: # EXEC: create a new eap64-basic-s2i application in OpenShift and have the jboss-kitchensink project imported to your workspace (dont use a pre-created one) # EXEC: create a server adapter for it Result: The server adapter immediately tries to start and publish once you finish the server adapter wizard. This leads to the following error which is expected since the pods, that the server adapter wants to publish to, dont exist yet. The build has to finish first. Once it's finished, the pod will be ready and available for the adapter to sync to. !starting-server-adapter-failed.png! The adapter then turns to [Stopped] and stays stopped. I then have to keep watching the OpenShift Explorer or the Properties to catch the moment when the build's finished and the service pod is running. Once this is achieved I can go and start the adapter which will then successfully publish. It would be much nicer if the adapter would do this waiting for me, it would possibly still inform me that the pod doesnt exist yet but would watch the build and start publishing once it exists. In order for this wait not to occur endlessly we could inform the user after some timeout, that we were waiting for some pods to appear but this didnt happen in the given timeframe. was: steps to reproduce: # EXEC: create a new eap64-basic-s2i application in OpenShift and have the jboss-kitchensink project imported to your workspace (dont use a pre-created one) # EXEC: create a server adapter for it Result: The server adapter immediately tries to start and publish once you finish the server adapter wizard. This leads to the following error which is expected since the pods, that the server adapter wants to publish to, dont exist yet. The build has to finish first. Once it's finished, the pod will be ready and available for the adapter to sync to. !! The adapter then turns to [Stopped] and stays stopped. I then have to keep watching the OpenShift Explorer or the Properties to catch the moment when the build's finished and the service pod is running. Once this is achieved I can go and start the adapter which will then successfully publish. It would be much nicer if the adapter would do this waiting for me, it would possibly still inform me that the pod doesnt exist yet but would watch the build and start publishing once it exists. In order for this wait not to occur endlessly we could inform the user after some timeout, that we were waiting for some pods to appear but this didnt happen in the given timeframe. > Server adapter: Should keep trying to start (silently) instead of erroring and giving up > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23782 > URL: https://issues.jboss.org/browse/JBIDE-23782 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > Attachments: starting-server-adapter-failed.png > > > steps to reproduce: > # EXEC: create a new eap64-basic-s2i application in OpenShift and have the jboss-kitchensink project imported to your workspace (dont use a pre-created one) > # EXEC: create a server adapter for it > Result: > The server adapter immediately tries to start and publish once you finish the server adapter wizard. This leads to the following error which is expected since the pods, that the server adapter wants to publish to, dont exist yet. The build has to finish first. Once it's finished, the pod will be ready and available for the adapter to sync to. > !starting-server-adapter-failed.png! > The adapter then turns to [Stopped] and stays stopped. > I then have to keep watching the OpenShift Explorer or the Properties to catch the moment when the build's finished and the service pod is running. > Once this is achieved I can go and start the adapter which will then successfully publish. > It would be much nicer if the adapter would do this waiting for me, it would possibly still inform me that the pod doesnt exist yet but would watch the build and start publishing once it exists. > In order for this wait not to occur endlessly we could inform the user after some timeout, that we were waiting for some pods to appear but this didnt happen in the given timeframe. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23782) Server adapter: Should keep trying to start (silently) instead of erroring and giving up

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23782: ---------------------------------------- Summary: Server adapter: Should keep trying to start (silently) instead of erroring and giving up Key: JBIDE-23782 URL: https://issues.jboss.org/browse/JBIDE-23782 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.3.AM1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 4.4.3.AM2 steps to reproduce: # EXEC: create a new eap64-basic-s2i application in OpenShift and have the jboss-kitchensink project imported to your workspace (dont use a pre-created one) # EXEC: create a server adapter for it Result: The server adapter immediately tries to start and publish once you finish the server adapter wizard. This leads to the following error which is expected since the pods, that the server adapter wants to publish to, dont exist yet. The build has to finish first. Once it's finished, the pod will be ready and available for the adapter to sync to. !! The adapter then turns to [Stopped] and stays stopped. I then have to keep watching the OpenShift Explorer or the Properties to catch the moment when the build's finished and the service pod is running. Once this is achieved I can go and start the adapter which will then successfully publish. It would be much nicer if the adapter would do this waiting for me, it would possibly still inform me that the pod doesnt exist yet but would watch the build and start publishing once it exists. In order for this wait not to occur endlessly we could inform the user after some timeout, that we were waiting for some pods to appear but this didnt happen in the given timeframe. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23781) Hibernate Console Configuration does not work for Version 5.2

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23781?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23781: ------------------------------ Fix Version/s: 4.4.3.AM2 > Hibernate Console Configuration does not work for Version 5.2 > ------------------------------------------------------------- > > Key: JBIDE-23781 > URL: https://issues.jboss.org/browse/JBIDE-23781 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.3.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.AM2 > > > When using Hibernate 5.2, the reverse engineering works ok but expanding the Hibernate Console Configuration or showing the mapping diagram results in an exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23781) Hibernate Console Configuration does not work for Version 5.2

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23781?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23781: --------------------------------- Assignee: Koen Aers > Hibernate Console Configuration does not work for Version 5.2 > ------------------------------------------------------------- > > Key: JBIDE-23781 > URL: https://issues.jboss.org/browse/JBIDE-23781 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.3.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > > When using Hibernate 5.2, the reverse engineering works ok but expanding the Hibernate Console Configuration or showing the mapping diagram results in an exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23781) Hibernate Console Configuration does not work for Version 5.2

by Koen Aers (JIRA)

Koen Aers created JBIDE-23781: --------------------------------- Summary: Hibernate Console Configuration does not work for Version 5.2 Key: JBIDE-23781 URL: https://issues.jboss.org/browse/JBIDE-23781 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.4.3.AM1 Reporter: Koen Aers When using Hibernate 5.2, the reverse engineering works ok but expanding the Hibernate Console Configuration or showing the mapping diagram results in an exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23780: ------------------------------------- Workaround Description: check and uncheck "Reuse existing repository". The checkbox "Reuse existing repository" will disappear all together with the error Workaround: Workaround Exists > Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23780 > URL: https://issues.jboss.org/browse/JBIDE-23780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png > > > steps to reproduce: > # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) > # EXEC: create a new application using the "eap64-basic-s2i" template > # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: > !clone-destination-already-exists.png! > # EXEC: manually remove the directory (ex. in cmd-line) > # EXEC: uncheck "Use default clone destination:" > Result: > The error wont go away, the wizard is still complaining even though the folder isnt in the way any more. > !error-even-though-clone-destination-doesnt-exist.png! > Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There' > s no way to work around this, you have to cancel the import and start over again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23780: ------------------------------------- Workaround Description: check and uncheck "Reuse existing repository". The checkbox "Reuse existing repository" will magically disappear all together with the error (was: check and uncheck "Reuse existing repository". The checkbox "Reuse existing repository" will disappear all together with the error ) > Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23780 > URL: https://issues.jboss.org/browse/JBIDE-23780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png > > > steps to reproduce: > # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) > # EXEC: create a new application using the "eap64-basic-s2i" template > # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: > !clone-destination-already-exists.png! > # EXEC: manually remove the directory (ex. in cmd-line) > # EXEC: uncheck "Use default clone destination:" > Result: > The error wont go away, the wizard is still complaining even though the folder isnt in the way any more. > !error-even-though-clone-destination-doesnt-exist.png! > Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There' > s no way to work around this, you have to cancel the import and start over again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23661) Inline the occurrences of org.jboss.tools.hibernate.runtime.spi.IValueVisitor

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23661?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23661. ------------------------------------ > Inline the occurrences of org.jboss.tools.hibernate.runtime.spi.IValueVisitor > ----------------------------------------------------------------------------- > > Key: JBIDE-23661 > URL: https://issues.jboss.org/browse/JBIDE-23661 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23780: ------------------------------------- Description: steps to reproduce: # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) # EXEC: create a new application using the "eap64-basic-s2i" template # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: !clone-destination-already-exists.png! # EXEC: manually remove the directory (ex. in cmd-line) # EXEC: uncheck "Use default clone destination:" Result: The error wont go away, the wizard is still complaining even though the folder isnt in the way any more. !error-even-though-clone-destination-doesnt-exist.png! Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There' s no way to work around this, you have to cancel the import and start over again. was: steps to reproduce: # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) # EXEC: create a new application using the "eap64-basic-s2i" template # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: !clone-destination-already-exists.png! # EXEC: manually remove the directory (ex. in cmd-line) # EXEC: uncheck "Use default clone destination:" Result: The error wont go away, the wizard is still complaining even though the folder isnt in the way any more !error-even-though-clone-destination-doesnt-exist.png! > Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23780 > URL: https://issues.jboss.org/browse/JBIDE-23780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png > > > steps to reproduce: > # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) > # EXEC: create a new application using the "eap64-basic-s2i" template > # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: > !clone-destination-already-exists.png! > # EXEC: manually remove the directory (ex. in cmd-line) > # EXEC: uncheck "Use default clone destination:" > Result: > The error wont go away, the wizard is still complaining even though the folder isnt in the way any more. > !error-even-though-clone-destination-doesnt-exist.png! > Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There' > s no way to work around this, you have to cancel the import and start over again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23780: ------------------------------------- Issue Type: Bug (was: Enhancement) > Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23780 > URL: https://issues.jboss.org/browse/JBIDE-23780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png > > > steps to reproduce: > # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) > # EXEC: create a new application using the "eap64-basic-s2i" template > # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: > !clone-destination-already-exists.png! > # EXEC: manually remove the directory (ex. in cmd-line) > # EXEC: uncheck "Use default clone destination:" > Result: > The error wont go away, the wizard is still complaining even though the folder isnt in the way any more > !error-even-though-clone-destination-doesnt-exist.png! -- 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