February 2013 - jbosstools-issues

[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 edited comment on JBIDE-13631 at 2/27/13 11:08 AM: -------------------------------------------------------------------- The url is extracted out of the creation log at object instance creation. If the cartridge has just been created, then the creation log is used. If we're looking for the url of an existing cartridge then the openshift-java-client is extracting it from the creation log. The lib is deciding upon info being *null* or not: {code:title=com.openshift.internal.client.EmbeddedCartridgeResource} private String extractUrl(String info, List<Message> messages) { if (info != null) { return extractUrl(info); } else { return extractUrl(messages); } } {code} *Unfortunately info is not "null" but "{}".* Therefore the code is using info instead of messages I highly suspect some format change in the platform. If the lib had taken messages, the url could have been extracted, since the messages contain the URL: {code} [ { "exit_code" => undefined, "field" => undefined, "severity" => "info", "text" => "Added mysql-5.1 to application 1361484901005" }, { "exit_code" => big integer 0, "field" => "result", "severity" => "info", "text" => " MySQL 5.1 database added. Please make note of these credentials: Root User: adminV15AnWB Root Password: 9DTqCwtcnc7f Database Name: 1361484901005 Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/ You can manage your new MySQL database by also embedding phpmyadmin-3.4. The phpmyadmin username and password will be the same as the MySQL credentials above. " }, { "exit_code" => big integer 0, "field" => "appinfo", "severity" => "info", "text" => "Connection URL: mysql://127.1.249.1:3306/ " } ], "status" => "created", "supported_api_versions" => [ big decimal 1.0, big decimal 1.1, big decimal 1.2, big decimal 1.3 ] {code} But even the our regex would have failed to extract the correct url. It extracted {code} mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/ {code} where it should have had extracted {code} mysql://127.1.249.1:3306/ {code} So here again, we have a change in the platform formats that causes our library to fail. was (Author: adietish): The url is extracted out of the creation log at object instance creation. If the cartridge has just been created, then the creation log is used. If we're looking for the url of an existing cartridge then the openshift-java-client is extracting it from the creation log. The lib is deciding upon info being *null* or not: {code:title=com.openshift.internal.client.EmbeddedCartridgeResource} private String extractUrl(String info, List<Message> messages) { if (info != null) { return extractUrl(info); } else { return extractUrl(messages); } } {code} !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *Unfortunately even info is not "null" but "{}".* Therefore the code is using info instead of messages I highly suspect some format change in the platform. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! If the lib had taken messages, the url could have been extracted, since the messages contain the URL: {code} [ { "exit_code" => undefined, "field" => undefined, "severity" => "info", "text" => "Added mysql-5.1 to application 1361484901005" }, { "exit_code" => big integer 0, "field" => "result", "severity" => "info", "text" => " MySQL 5.1 database added. Please make note of these credentials: Root User: adminV15AnWB Root Password: 9DTqCwtcnc7f Database Name: 1361484901005 Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/ You can manage your new MySQL database by also embedding phpmyadmin-3.4. The phpmyadmin username and password will be the same as the MySQL credentials above. " }, { "exit_code" => big integer 0, "field" => "appinfo", "severity" => "info", "text" => "Connection URL: mysql://127.1.249.1:3306/ " } ], "status" => "created", "supported_api_versions" => [ big decimal 1.0, big decimal 1.1, big decimal 1.2, big decimal 1.3 ] {code} But even the our regex would have failed to extract the correct url. It extracted {code} mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/ {code} where it should have had extracted {code} mysql://127.1.249.1:3306/ {code} So here again, we have a change in the platform formats that causes our library to fail. > 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, 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13669) add refactored m2e-wtp features to JBT Central community feature as dependencies so they'll be installed OOTB

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13669?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13669: ------------------------------- Description: Must add these as requirements to org.jboss.tools.community.central.feature: https://github.com/jbosstools/jbosstools-central/blob/master/central/feat... * org.eclipse.m2e.wtp.jsf.feature * org.eclipse.m2e.wtp.jaxrs.feature * org.eclipse.m2e.wtp.jpa.feature Changed... Moving this dependency to org.jboss.tools.maven.project.examples.feature instead. was: Must add these as requirements to org.jboss.tools.community.central.feature: https://github.com/jbosstools/jbosstools-central/blob/master/central/feat... * org.eclipse.m2e.wtp.jsf.feature * org.eclipse.m2e.wtp.jaxrs.feature * org.eclipse.m2e.wtp.jpa.feature > add refactored m2e-wtp features to JBT Central community feature as dependencies so they'll be installed OOTB > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13669 > URL: https://issues.jboss.org/browse/JBIDE-13669 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Labels: respin-c > Fix For: 4.1.0.Alpha1 > > > Must add these as requirements to org.jboss.tools.community.central.feature: > https://github.com/jbosstools/jbosstools-central/blob/master/central/feat... > * org.eclipse.m2e.wtp.jsf.feature > * org.eclipse.m2e.wtp.jaxrs.feature > * org.eclipse.m2e.wtp.jpa.feature > Changed... > Moving this dependency to org.jboss.tools.maven.project.examples.feature instead. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13569) Error when waiting for application to become reachable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13569?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13569: ------------------------------------------------- Bill DeCoste <wdecoste(a)redhat.com> made a comment on [bug 895507|https://bugzilla.redhat.com/show_bug.cgi?id=895507] There's no code reuse since the /health logic is per independent cartridge. The ability to control Apache is going away with the new cartridge design so as we roll out the new cartridges the /health check is going away too unless it's deployed in the carts themselves which has been the whole problem. > Error when waiting for application to become reachable > ------------------------------------------------------ > > Key: JBIDE-13569 > URL: https://issues.jboss.org/browse/JBIDE-13569 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: error-waiting-for-reachable.png, JBT_0219.png > > > {code} > com.openshift.client.NotFoundOpenShiftException: Could not find any OpenShift resource at "http://testapp-1360837500661.rhcloud.com/health" > at com.openshift.internal.client.RestService.request(RestService.java:101) > at com.openshift.internal.client.ApplicationResource.waitForPositiveHealthResponse(ApplicationResource.java:510) > at com.openshift.internal.client.ApplicationResource.waitForAccessible(ApplicationResource.java:487) > at org.jboss.tools.openshift.express.internal.ui.job.WaitForApplicationJob.doRun(WaitForApplicationJob.java:50) > at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:35) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: com.openshift.internal.client.httpclient.NotFoundException: Could not find resource "http://testapp-1360837500661.rhcloud.com/health" > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:96) > at com.openshift.internal.client.RestService.request(RestService.java:139) > at com.openshift.internal.client.RestService.request(RestService.java:97) > ... 5 more > Caused by: java.io.FileNotFoundException: http://testapp-1360837500661.rhcloud.com/health > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94) > ... 7 more > {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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13669) add refactored m2e-wtp features to JBT Central community feature as dependencies so they'll be installed OOTB

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13669: ---------------------------------- Summary: add refactored m2e-wtp features to JBT Central community feature as dependencies so they'll be installed OOTB Key: JBIDE-13669 URL: https://issues.jboss.org/browse/JBIDE-13669 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Snjezana Peco Fix For: 4.1.0.Alpha1 Must add these as requirements to org.jboss.tools.community.central.feature: https://github.com/jbosstools/jbosstools-central/blob/master/central/feat... * org.eclipse.m2e.wtp.jsf.feature * org.eclipse.m2e.wtp.jaxrs.feature * org.eclipse.m2e.wtp.jpa.feature -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13639) remove struts tests from integration-tests update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13639?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13639: ---------------------------------- Assignee: Martin Malina (was: Len DiMaggio) > remove struts tests from integration-tests update site > ------------------------------------------------------ > > Key: JBIDE-13639 > URL: https://issues.jboss.org/browse/JBIDE-13639 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, struts/shale > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-integration-tests.aggregate_master/53/console} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier requires 'bundle org.jboss.tools.struts.ui 3.1.0' but it could not be found > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier to bundle org.jboss.tools.struts.ui 3.1.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] > {code} > This is failing because struts has been removed from the upstream sites (it's been removed from JBT4.1/JBDS 7). So, need to also remove it from your integration tests site's category.xml file [1]. > [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-10398) OpenShift Express : Can not delete git project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10398?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10398: ------------------------------------- Fix Version/s: 4.0.1.Final (was: 4.1.x) > OpenShift Express : Can not delete git project > ---------------------------------------------- > > Key: JBIDE-10398 > URL: https://issues.jboss.org/browse/JBIDE-10398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 3.3.0.M5 > Environment: windows 7 (most likely all windows flavors) > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.0.1.Final > > Attachments: openshift.ogv > > > Whenever I try to physically delete my openshift project from the workspace, I get a popup with the following errors : > {noformat} > Problems encountered while deleting resources. > Could not delete '/hello/.git'. > Problems encountered while deleting resources. > Problems encountered while deleting files. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack\pack-10eb864ff7ab3a1edfc8b868c90a743fdee571db.pack. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects. > Could not delete: C:\Users\Fred Bricon\git\hello\.git. > Could not delete 'C:\Users\Fred Bricon\git\hello'. > {noformat} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13668) openshift-java-client: fix failing unit-test ApplicationResourceTest#shouldWaitUntilTimeout

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13668: ---------------------------------------- Summary: openshift-java-client: fix failing unit-test ApplicationResourceTest#shouldWaitUntilTimeout Key: JBIDE-13668 URL: https://issues.jboss.org/browse/JBIDE-13668 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 current output when building openshift-java-client which runs the unit-tests (not the integration tests): {code} Tests run: 138, Failures: 1, Errors: 0, Skipped: 36, Time elapsed: 3.983 sec <<< FAILURE! Results : Failed tests: shouldWaitUntilTimeout(com.openshift.internal.client.ApplicationResourceTest) Tests run: 138, Failures: 1, Errors: 0, Skipped: 36 [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10.666s [INFO] Finished at: Wed Feb 27 15:12:58 CET 2013 {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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13408: ---------------------------------------- The generate-repository-facade execution was moved to parent. The following pull requests remove the execution from individual sites: * https://github.com/jbosstools/jbosstools-central/pull/67 * https://github.com/jbosstools/jbosstools-base/pull/54 * https://github.com/jbosstools/jbosstools-server/pull/56 * https://github.com/jbosstools/jbosstools-javaee/pull/56 > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {quote} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-11270) Remote branch to use should be a text-field with autocomplete (OpenShift server editor and import/creation wizard)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11270?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11270: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Alpha1) > Remote branch to use should be a text-field with autocomplete (OpenShift server editor and import/creation wizard) > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-11270 > URL: https://issues.jboss.org/browse/JBIDE-11270 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: egit-remote-branches.png, remote-disabled.png, server_detail.jpg > > > When you open the detail of OpenShift server adapter you can change the Git remote name by typing the new value. Could you change the text field to combo box filled with remote names that are actually configured for the OpenShift project? > !server_detail.jpg! > We decided to match what EGit provides: a text-field which allows freely typed entries (which would create new branches) but also offers auto-completion to match existing branches. > !egit-remote-branches.png! -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-11270) Remote branch to use should be a text-field with autocomplete (OpenShift server editor and import/creation wizard)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11270?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11270: ------------------------------------------ reopened and set fix-version to 4.1.x > Remote branch to use should be a text-field with autocomplete (OpenShift server editor and import/creation wizard) > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-11270 > URL: https://issues.jboss.org/browse/JBIDE-11270 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: egit-remote-branches.png, remote-disabled.png, server_detail.jpg > > > When you open the detail of OpenShift server adapter you can change the Git remote name by typing the new value. Could you change the text field to combo box filled with remote names that are actually configured for the OpenShift project? > !server_detail.jpg! > We decided to match what EGit provides: a text-field which allows freely typed entries (which would create new branches) but also offers auto-completion to match existing branches. > !egit-remote-branches.png! -- 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, 1 month

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