January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16356) OpenShift project wizard does not handle a dirty/modified git project gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16356: ---------------------------------------- Summary: OpenShift project wizard does not handle a dirty/modified git project gracefully (was: To Commit or not to Commit) > OpenShift project wizard does not handle a dirty/modified git project gracefully > -------------------------------------------------------------------------------- > > Key: JBIDE-16356 > URL: https://issues.jboss.org/browse/JBIDE-16356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Attachments: contacts-mobile-basic.zip > > > I am getting an odd error message. > Here are the steps: > 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git > 2) git checkout WFK-113 > 3) JBDS 7.1 import as Maven project > 4) tweak the pom.xml (it was broken but now fixed) > 5) it deploys to a local EAP, now attempt to send to OpenShift > 6) run the OpenShift wizard as seen in the video > http://screencast.com/t/NVTPK4pL -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16356) To Commit or not to Commit

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16356: --------------------------------------------- [~burrsutter] your zip has not .git directory in it - did you not zip everything ? My assumption is you somehow has some dirty state that the wizard is not accounting for. When you are trying to git commit via eclipse it shows up with a few files that looks like they have been deleted (there is a cross on them) and my guess is that is the one it is complaining about. If you could get the *full* zip to us - one that has the relevant .git dir included it would be faster to determine. > To Commit or not to Commit > -------------------------- > > Key: JBIDE-16356 > URL: https://issues.jboss.org/browse/JBIDE-16356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Attachments: contacts-mobile-basic.zip > > > I am getting an odd error message. > Here are the steps: > 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git > 2) git checkout WFK-113 > 3) JBDS 7.1 import as Maven project > 4) tweak the pom.xml (it was broken but now fixed) > 5) it deploys to a local EAP, now attempt to send to OpenShift > 6) run the OpenShift wizard as seen in the video > http://screencast.com/t/NVTPK4pL -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16357) RemoteSystemsTempFiles is possible to choose in OpenShift select project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16357?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16357: ---------------------------------------- Summary: RemoteSystemsTempFiles is possible to choose in OpenShift select project (was: RemoteSystemsTempFiles) > RemoteSystemsTempFiles is possible to choose in OpenShift select project > ------------------------------------------------------------------------ > > Key: JBIDE-16357 > URL: https://issues.jboss.org/browse/JBIDE-16357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > > The Select Existing Project dialog should not display > RemoteSystemTempFiles as an option > http://screencast.com/t/CKEnB16Rbad -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16357) RemoteSystemsTempFiles

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16357?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16357: --------------------------------------------- I don't think there is a way for us to distinguish this project from others - if there are then sure, but I think there is more than just this project. btw. I assume this is in the OpenShift Wizard ? I'll update the title to reflect that. > RemoteSystemsTempFiles > ---------------------- > > Key: JBIDE-16357 > URL: https://issues.jboss.org/browse/JBIDE-16357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > > The Select Existing Project dialog should not display > RemoteSystemTempFiles as an option > http://screencast.com/t/CKEnB16Rbad -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16355: --------------------------------------------- the sf.net location is used for our archival of updatesite zips etc., they aren't archived/mirrored anywhere else. This issue is not about usage of sf.net (we can take that in a different jira if you want), this one is about the zz_release_notes*.html. The advantage of the html file is that it is a snapshot and wont change, where as the result of a jira query might. But I would say just linking to the jira release notes would be fine. About the links in JBDS 7.1 then those does not actually cover all the resolved issues since it looks only on Bugs, not on feature requests. Also it seems weird why we don't just provide a link to these and not only document how they can make their own query ? I would use a link like this: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=10020&version=... This shows all the various type of issues that was resolved with the fix version of 4.1.1.CR1 in this case. > replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query > -------------------------------------------------------------------------------------- > > Key: JBIDE-16355 > URL: https://issues.jboss.org/browse/JBIDE-16355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Re: files like: > http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/... > {quote} > (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees > (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;) > (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these. > (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean. > (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;) > (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this. > {quote} > Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query. > That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final). > We can also produce a query for both JBT and JBDS. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16290: ------------------------------------- Attachment: Java - Eclipse _001.png > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16290 at 1/15/14 5:59 AM: ------------------------------------------------------------------- For me (running latest Fedora 20) Luna/GTK3 is not usable at all, all views are empty: !Java - Eclipse _001.png! It turned out that GTK 3.10 used on FC20 has issues they dont know how to solve yet: https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 was (Author: adietish): For me (running latest Fedora 20) Luna/GTK3 is not usable at all. It turned out that GTK 3.10 used on FC20 has issues they dont know how to solve yet: https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16290 at 1/15/14 5:57 AM: ------------------------------------------------------------------- For me (running latest Fedora 20) Luna/GTK3 is not usable at all. It turned out that GTK 3.10 used on FC20 has issues they dont know how to solve yet: https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 was (Author: adietish): For me GTK3 is not usable at all. I'm running Fedora 20 and Eclipse Luna is unusable on it. It turned out that GTK 3.10 used on FC20 has issues they dont know how to solve yet: https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > Attachments: luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16290 at 1/15/14 5:56 AM: ------------------------------------------------------------------- Furthermore WebKit is crashing my Luna (I'm running latest Fedora 20). This started as soon as I installed the google-talk plugin into my google-chrome. Luna (and Kepler) froze and crashed as soon as I: 1) triggered autocomplete in a Java code editor (see [^luna-crashing-on-outcomplete.ogv] freezing at 0:24 and crashing) 2) tried to switch the browser in the Eclipse preferences (pick "Web Browser" in Eclipse preferences and boom!) See https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123 Our guys working on fixing SWT/GTK3 have a patch that should help here. Their approach is to have webkit running in a separate process. In a birds perspective this sounds to me as if this should help not crashing the IDE but not sure if this helps for webkit crashing. was (Author: adietish): Furthermore WebKit is crashing my Luna. This started as soon as I installed the google-talk plugin into my google-chrome. Luna (and Kepler) froze and crashed as soon as I: 1) triggered autocomplete in a Java code editor (see [^luna-crashing-on-outcomplete.ogv] freezing at 0:24 and crashing) 2) tried to switch the browser in the Eclipse preferences (pick "Web Browser" in Eclipse preferences and boom!) Our guys working on fixing SWT/GTK3 have a patch that should help here. Their approach is to have webkit running in a separate process. In a birds perspective this sounds to me as if this should help not crashing the IDE but not sure if this helps for webkit crashing. > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > Attachments: luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16290 at 1/15/14 5:53 AM: ------------------------------------------------------------------- Furthermore WebKit is crashing my Luna. This started as soon as I installed the google-talk plugin into my google-chrome. Luna (and Kepler) froze and crashed as soon as I: 1) triggered autocomplete in a Java code editor (see [^luna-crashing-on-outcomplete.ogv] freezing at 0:24 and crashing) 2) tried to switch the browser in the Eclipse preferences (pick "Web Browser" in Eclipse preferences and boom!) Our guys working on fixing SWT/GTK3 have a patch that should help here. Their approach is to have webkit running in a separate process. In a birds perspective this sounds to me as if this should help not crashing the IDE but not sure if this helps for webkit crashing. was (Author: adietish): Furthermore WebKit is crashing my Luna. This started as soon as I installed the google-talk plugin into my google-chrome. Luna (and Kepler) froze and crashed as soon as I: 1) triggered autocomplete in a Java code editor 2) tried to switch the browser in the Eclipse preferences (pick "Web Browser" in Eclipse preferences and boom!) Our guys working on fixing SWT/GTK3 have a patch that should help here. Their approach is to have webkit running in a separate process. In a birds perspective this sounds to me as if this should help not crashing the IDE but not sure if this helps for webkit crashing. > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > Attachments: luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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

12 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 2014