February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13664: ------------------------------------- Fix Version/s: 4.1.0.Alpha2 > tracing options for openshift client not showing up > --------------------------------------------------- > > 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 > Fix For: 4.1.0.Alpha2 > > > tracing options in .options in openshiftclient is not showing up -- 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-13653) Eclipse freezes after 'ctrl + 4' command

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13653?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13653: ------------------------------ Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Alpha1) > Eclipse freezes after 'ctrl + 4' command > ----------------------------------------- > > Key: JBIDE-13653 > URL: https://issues.jboss.org/browse/JBIDE-13653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > Attachments: stack.txt > > -- 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-13663) Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13663?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-13663: ---------------------------------------- Assignee: Andre Dietisheim > Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13663 > URL: https://issues.jboss.org/browse/JBIDE-13663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > usecase: > EXECUTE: Create openshift project > EXECUTE: Make sure all is committed and Pushed. > EXECUTE: Edit an existing committed file - commit it. > EXECUTE: Add a "xyz.log" file that is not to be committed. > EXECUTE: Publish to server. > ASSERT: no message about dirty changes, everything should be committed. Only message about push is missing. > EXECUTE: Wait for publish to finish. > ASSERT: "xyz.log" should *not* be pushed nor committed. -- 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-13663) Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13663: ------------------------------------------- Summary: Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files Key: JBIDE-13663 URL: https://issues.jboss.org/browse/JBIDE-13663 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen usecase: EXECUTE: Create openshift project EXECUTE: Make sure all is committed and Pushed. EXECUTE: Edit an existing committed file - commit it. EXECUTE: Add a "xyz.log" file that is not to be committed. EXECUTE: Publish to server. ASSERT: no message about dirty changes, everything should be committed. Only message about push is missing. EXECUTE: Wait for publish to finish. ASSERT: "xyz.log" should *not* be pushed nor committed. -- 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-13606) Java EE Web Project Wizard does not set target runtime when user selected one

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13606?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-13606. ------------------------------ > Java EE Web Project Wizard does not set target runtime when user selected one > ----------------------------------------------------------------------------- > > Key: JBIDE-13606 > URL: https://issues.jboss.org/browse/JBIDE-13606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final > Environment: Fedora 17, JDK1.7, JBDS 6.0.0 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha1 > > Attachments: TargetRuntime1.png, TargetRuntime2.png > > > I chose jboss-eap-6.0 Runtime as the target runtime in the Java EE Web Project wizard, but this was then not set in the project's properties when the project was created. I had to go and set it manually. > Original (perhaps confusing) description: > [In the Java EE Web Project wizard I chose jboss-eap-6.0 Runtime as the target runtime. When the wizard completed there were several warnings. One in particular: > "Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment." > This warning was resolved by setting the target runtime to jboss-eap-6.0 again in the project's Properties > Targeted Runtimes. > So although I had chosen jboss-eap-6.0 Runtime as the target runtime in the wizard, this was not set in the project's properties when the project was created. As a user, this seems like counter-intuitive behavior. I would have thought it would have been set.] -- 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-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: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 895507|https://bugzilla.redhat.com/show_bug.cgi?id=895507] Bill, I guess that doing it for all apps is a good idea since this would ensure existing JBDS users would be able to work with every app type, regardless the template being used. I guess using the same pattern for all apps would also be beneficial for your code? > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2404) JBDS crashes at startup when a BPEL diagram was open upon previous shutdown

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2404?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2404: ------------------------------------------- This is possibly a bug in eclipse SWT core that causes it but since its indigo no patches made - would need to worked around in BPEL tooling afaics. > JBDS crashes at startup when a BPEL diagram was open upon previous shutdown > --------------------------------------------------------------------------- > > Key: JBDS-2404 > URL: https://issues.jboss.org/browse/JBDS-2404 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA, 5.0.1.GA > Environment: Linux (Ubuntu 12.10, 64-bit), Oracle JVM (1.6.0_37 and 1.7.0_09, 64-bit) > Also 32 bit ubuntu 12.10 > Reporter: Maurice de Chateau > Assignee: Robert (Bob) Brodt > Fix For: 5.0.1.GA-SOA > > Attachments: crash with BPEL diagram.log, crash with jdk 6.log, CreditReport.wsdl, CreditReportProcess.bpel > > > In JBDS 5.0.x with ´SOA and Data Services Tooling´ installed, the IDE cannot be started up once it was previously closed with a BPEL diagram still opened. -- 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] (JBDS-2404) JBDS crashes at startup when a BPEL diagram was open upon previous shutdown

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2404?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2404: -------------------------------------- Fix Version/s: 5.0.1.GA-SOA (was: 5.0.2.GA) > JBDS crashes at startup when a BPEL diagram was open upon previous shutdown > --------------------------------------------------------------------------- > > Key: JBDS-2404 > URL: https://issues.jboss.org/browse/JBDS-2404 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA, 5.0.1.GA > Environment: Linux (Ubuntu 12.10, 64-bit), Oracle JVM (1.6.0_37 and 1.7.0_09, 64-bit) > Also 32 bit ubuntu 12.10 > Reporter: Maurice de Chateau > Assignee: Robert (Bob) Brodt > Fix For: 5.0.1.GA-SOA > > Attachments: crash with BPEL diagram.log, crash with jdk 6.log, CreditReport.wsdl, CreditReportProcess.bpel > > > In JBDS 5.0.x with ´SOA and Data Services Tooling´ installed, the IDE cannot be started up once it was previously closed with a BPEL diagram still opened. -- 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-13641) tycho plugin snapshot 0.0.1 disappeared - causing failing builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13641?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13641: ---------------------------------------- The general solution about this issue is to not use SNAPSHOT stuff from Nexus. 0.16.0.CR1 was released. site/pom.xml containing reference to 0.16.0-SNAPSHOT on jbosstools-4.0.x branches were updated (Pull Request were sent) On master, we're suggesting a refactoring that make that components don't have to configure this plugin and set version no more: https://github.com/jbosstools/jbosstools-build/pull/71 > tycho plugin snapshot 0.0.1 disappeared - causing failing builds > ---------------------------------------------------------------- > > Key: JBIDE-13641 > URL: https://issues.jboss.org/browse/JBIDE-13641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > snapshots gets purged every 90-days and our builds were using old snapshot. > for 4.1.0.Alpha1x i'll do the minimal fix but for 4.0.x and 4.1.x we need a more permanent solution. -- 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-13639) remove struts tests from integration-tests update site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13639?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13639: ---------------------------------------- Assignee: Len DiMaggio (was: Max Rydahl Andersen) Component/s: Build/Releng struts/shale (was: testing) Len - we need to get master of integration test to stop referencing struts. Test for struts should stay in the branch but master should get them removed. Nick - testing component is not for QE testing but for testing tools (like arquillian,jsfunit etc.). I'm going to rename that so we stop putting unrelated stuff into it. > 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: Len DiMaggio > 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, 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