February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13664 at 2/28/13 5:25 PM: ------------------------------------------------------------------- yes, it solved it, great, thanks! I did a "mvn clean install" in my plugins and pointed a vanilla Juno-SR1 to the freshly build repo (while adding the JBT nightlies updates site). Tracing for the OpenShift client then became available in the preferences: !openshift-tracing-available.png! and once the flag were set to *true*, tracing output was produced: {code} tail -f /home/adietish/workspace/.metadata/trace.log | Worker-1 | 2013-02-28 23:22:48.519 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Requesting GET on https://openshift.redhat.com/broker/rest/user | | Worker-1 | 2013-02-28 23:22:48.520 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | creating connection to https://openshift.redhat.com/broker/rest/user using username "<USERNAME>" and password "<PASSWORD>" | | Worker-1 | 2013-02-28 23:22:49.764 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Unmarshalling response {"data":{"capabilities":{"subaccounts":false,"gear_sizes":["small","medium"]},"consumed_gears":2,"links":{"LIST_KEYS":{"href":"https://openshift.redhat.com/broker/rest/user/keys","method":"GET","optional_params":[],"rel":"Get SSH keys","required_params":[]},"ADD_KEY":{"href":"https://openshift.redhat.com/broker/rest/user/keys","method":"POST","optional_params":[],"rel":"Add new SSH key","required_params":[{"description":"Name of the key","invalid_options":[],"name":"name","type":"string","valid_options":[]},{"description":"Type of Key","invalid_options":[],"name":"type","type":"string","valid_options":["ssh-rsa","ssh-dss","ecdsa-sha2-nistp256-cert-v01(a)openssh.com","ecdsa-sha2-nistp384-cert-v01(a)openssh.com","ecdsa-sha2-nistp521-cert-v01(a)openssh.com","ssh-rsa-cert-v01(a)openssh.com","ssh-dss-cert-v01(a)openssh.com","ssh-rsa-cert-v00(a)openssh.com","ssh-dss-cert-v00(a)openssh.com","ecdsa-sha2-nistp256","ecdsa-sha2-nistp384","ecdsa-sha2-nistp521"]},{"description":"The key portion of an rsa key (excluding ssh-rsa and comment)","invalid_options":[],"name":"content","type":"string","valid_options":[]}]}},"login":"adietish(a)redhat.com","max_gears":10,"plan_id":"freeshift","usage_account_id":null},"messages":[],"status":"ok","supported_api_versions":[1.0,1.1,1.2,1.3],"type":"user","version":"1.0"} | | Worker-1 | 2013-02-28 23:22:49.774 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Requesting GET on https://openshift.redhat.com/broker/rest/domains | | Worker-1 | 2013-02-28 23:22:49.776 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | creating connection to https://openshift.redhat.com/broker/rest/domains using username "<USERNAME>" and password "<PASSWORD>" | | Worker-1 | 2013-02-28 23:22:50.987 | org.jboss.tools.openshift.express.client | /debug/client | org.jboss.tools.openshift.express.client.internal.log.Trace | trace | 66 | Unmarshalling response {"data":[{"id":"honkabonka2","links":{"GET":{"href":"https://openshift.redhat.com/broker/rest/domains/honkabonka2","method":"GET","optional_params":[],"rel":"Get domain","required_params":[]},"LIST_APPLICATIONS":{"href":"https://openshift.redhat.com/broker/rest/domains/honkabonka2/applications","method":"GET","optional_params":[],"rel":"List applications","required_params":[]},"ADD_APPLICATION":{"href":"https://openshift.redhat.com/broker/rest/domains/honkabonka2/applications","method":"POST","optional_params":[{"default_value":null,"description":"framework-type, e.g: php-5.3","name":"cartridge","type":"string","valid_options":["nodejs-0.6","jbossews-2.0","zend-5.6","ruby-1.9","python-3.3","jbossas-7","python-2.6","jenkins-1.4","ruby-1.8","python-2.7","jbosseap-6.0","diy-0.1","jbossews-1.0","php-5.3","perl-5.10"]},{"default_value":false,"description":"Mark application as scalable","name":"scale","type":"boolean","valid_options":[true,false]},{"default_value":"small","description":"The size of the gear","name":"gear_profile","type":"string","valid_options":["small","medium"]}],"rel":"Create new application","required_params":[{"description":"Name of the application","invalid_options":["amentra","aop","apiviz","arquillian","blacktie","boxgrinder","byteman","cirras","cloud","cloudforms","cygwin","davcache","dogtag","drools","drools","ejb3","errai","esb","fedora","freeipa","gatein","git","gfs","gravel","guvnor","hibernate","hornetq","iiop","infinispan","ironjacamar","javassist","jbcaa","jbcd","jboss","jbpm","jdcom","jgroups","jmx","jopr","jrunit","jsfunit","kosmos","liberation","makara","mass","maven","metajizer","metamatrix","mobicents","mod_cluster","modeshape","mugshot","mysql","netty","openshift","osgi","overlord","ovirt","penrose","picketbox","picketlink","portletbridge","portletswap","posse","pressgang","qumranet","railo","redhat","resteasy","rhca","rhcds","rhce","rhcsa","rhcss","rhct","rhcva","rhel","rhev","rhq","rhx","richfaces","riftsaw","savara","scribble","seam","shadowman","shotoku","shrinkwrap","snowdrop","solidice","spacewalk","spice","steamcannon","stormgrind","switchyard","tattletale","teiid","tohu","torquebox","weld","wise","xnio"],"name":"name","type":"string","valid_options":[]}]},"UPDATE":{"href":"https://openshift.redhat.com/broker/rest/domains/honkabonka2","method":"PUT","optional_params":[],"rel":"Update domain","required_params":[{"description":"Name of the domain","invalid_options":[],"name":"id","type":"string","valid_options":[]}]},"DELETE":{"href":"https://openshift.redhat.com/broker/rest/domains/honkabonka2","method":"DELETE","optional_params":[{"default_value":false,"description":"Force delete domain. i.e. delete any applications under this domain","name":"force","type":"boolean","valid_options":[true,false]}],"rel":"Delete domain","required_params":[]}},"suffix":"rhcloud.com"}],"messages":[],"status":"ok","supported_api_versions":[1.0,1.1,1.2,1.3],"type":"domains","version":"1.0"} {code} was (Author: adietish): yes, it solved it, great, thanks! I did a "mvn clean install" in my plugins and pointed a vanilla Juno-SR1 to the freshly build repo (while adding the JBT nightlies updates site). Tracing for the OpenShift client then became available in the preferences: !openshift-tracing-available.png! > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > Attachments: openshift-tracing-available.png > > > tracing options in .options in openshiftclient is not showing up. > And when starting with -debug .options > and .options contains: > org.jboss.tools.openshift.express.client/debug=true > org.jboss.tools.openshift.express.client/debug/client=true > You get: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > So this is not working at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13664 at 2/28/13 5:15 PM: ------------------------------------------------------------------- yes, it solved it, great, thanks! I did a "mvn clean install" in my plugins and pointed a vanilla Juno-SR1 to the freshly build repo (while adding the JBT nightlies updates site). Tracing for the OpenShift client then became available in the preferences: !openshift-tracing-available.png! was (Author: adietish): yes, it solved it, great, thanks! Tracing is now available: !openshift-tracing-available.png! > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > Attachments: openshift-tracing-available.png > > > tracing options in .options in openshiftclient is not showing up. > And when starting with -debug .options > and .options contains: > org.jboss.tools.openshift.express.client/debug=true > org.jboss.tools.openshift.express.client/debug/client=true > You get: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > So this is not working at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13664: ------------------------------------------ yes, it solved it, great, thanks! Tracing is now available: !openshift-tracing-available.png! > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > Attachments: openshift-tracing-available.png > > > tracing options in .options in openshiftclient is not showing up. > And when starting with -debug .options > and .options contains: > org.jboss.tools.openshift.express.client/debug=true > org.jboss.tools.openshift.express.client/debug/client=true > You get: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > So this is not working at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13664: ------------------------------------- Attachment: openshift-tracing-available.png > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > Attachments: openshift-tracing-available.png > > > tracing options in .options in openshiftclient is not showing up. > And when starting with -debug .options > and .options contains: > org.jboss.tools.openshift.express.client/debug=true > org.jboss.tools.openshift.express.client/debug/client=true > You get: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > So this is not working at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13681) compile failed in org.jboss.tools.jst.web.ui

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13681?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13681: ------------------------------------ Aggregated: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ Composite: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... Latest Base build in master branch: 4.1.0 Alpha1-v20130227-1443-B172 Latest JST build using upstream Base B172: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... (Feb 28, 2013 7:41:43 AM) Uses composite site to resolve upstream JBT deps: {code} [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/al... (0B of 18.93kB at 0B/s) {code} As you can see, it's pulling from the stable branch (_41) instead of trunk (_master). Why? Because you're using the wrong parent pom: {code} Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... {code} So... fix your root pom to point at the Alpha2 version and you should be fine. > compile failed in org.jboss.tools.jst.web.ui > -------------------------------------------- > > Key: JBIDE-13681 > URL: https://issues.jboss.org/browse/JBIDE-13681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-jst_master/309/console} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.jst.web.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-jst_master/sources/plugins/org.jboss.tools.jst.web.ui/src/org/jboss/tools/jst/web/ui/palette/html/jquery/wizard/JQueryFieldEditorFactory.java:[84,0] > [ERROR] text.setMessage("Generate"); > [ERROR] ^^^^^^^^^^ > [ERROR] The method setMessage(String) is undefined for the type TextFieldEditor > [ERROR] 1 problem (1 error) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13681) compile failed in org.jboss.tools.jst.web.ui

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13681?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13681 at 2/28/13 4:50 PM: ------------------------------------------------------------- Aggregated: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ Composite: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... Latest Base build in master branch: 4.1.0 Alpha1-v20130227-1443-B172 Latest JST build using upstream Base B172: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... (Feb 28, 2013 7:41:43 AM) Uses composite site to resolve upstream JBT deps: {code} [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/al... (0B of 18.93kB at 0B/s) {code} As you can see, it's pulling from the stable branch (_41) instead of trunk (_master). Why? *Because you're using the wrong parent pom version*: {code} Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... {code} So... fix your root pom to point at the Alpha2 version and you should be fine. was (Author: nickboldt): Aggregated: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/ Composite: http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... Latest Base build in master branch: 4.1.0 Alpha1-v20130227-1443-B172 Latest JST build using upstream Base B172: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... (Feb 28, 2013 7:41:43 AM) Uses composite site to resolve upstream JBT deps: {code} [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/al... (0B of 18.93kB at 0B/s) {code} As you can see, it's pulling from the stable branch (_41) instead of trunk (_master). Why? Because you're using the wrong parent pom: {code} Downloading: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... {code} So... fix your root pom to point at the Alpha2 version and you should be fine. > compile failed in org.jboss.tools.jst.web.ui > -------------------------------------------- > > Key: JBIDE-13681 > URL: https://issues.jboss.org/browse/JBIDE-13681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-jst_master/309/console} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.jst.web.ui: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-jst_master/sources/plugins/org.jboss.tools.jst.web.ui/src/org/jboss/tools/jst/web/ui/palette/html/jquery/wizard/JQueryFieldEditorFactory.java:[84,0] > [ERROR] text.setMessage("Generate"); > [ERROR] ^^^^^^^^^^ > [ERROR] The method setMessage(String) is undefined for the type TextFieldEditor > [ERROR] 1 problem (1 error) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13631: ------------------------------------- Bugzilla Update: (was: Perform) > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13631: ------------------------------------------ added integration tests to openshift-java-client in https://github.com/openshift/openshift-java-client/pull/23 > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13631: ------------------------------------------ As commented above, the connection URL is now reported differently, depending on when the URL is requested. * In the "session" when the cartridge was created (mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT): !mysql-url-at-creation.png! * In latter "sessions" (mysql://127.11.220.3:3306/): !mysql-url-after-creation.png! Afaik this is only the case for PostgreSQL and MySQL (not mongoDB). > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13631: ------------------------------------- Attachment: mysql-url-at-creation.png mysql-url-after-creation.png > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 February 2013