August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20524) Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20524?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20524: ----------------------------------- Forum Reference: https://developer.jboss.org/message/938755 > Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0) > ------------------------------------------------------------------ > > Key: JBIDE-20524 > URL: https://issues.jboss.org/browse/JBIDE-20524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Blocker > Labels: upstream > Fix For: 4.3.0.CR1 > > > Upstream regression Mars 4.5.0 XULRunner [Bug 472956|https://bugs.eclipse.org/bugs/show_bug.cgi?id=472956] > Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20524) Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20524?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20524: ----------------------------------- Component/s: upstream > Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0) > ------------------------------------------------------------------ > > Key: JBIDE-20524 > URL: https://issues.jboss.org/browse/JBIDE-20524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Blocker > Labels: upstream > Fix For: 4.3.0.CR1 > > > Upstream regression Mars 4.5.0 XULRunner [Bug 472956|https://bugs.eclipse.org/bugs/show_bug.cgi?id=472956] > Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20524) Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20524?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-20524: -------------------------------- Description: Upstream regression Mars 4.5.0 XULRunner [Bug 472956|https://bugs.eclipse.org/bugs/show_bug.cgi?id=472956] Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 was: Upstream regression Mars 4.5.0 XULRunner [Bug 472956|http://atlassian.com]https://bugs.eclipse.org/bugs/show_bug.cgi?id... Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 > Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0) > ------------------------------------------------------------------ > > Key: JBIDE-20524 > URL: https://issues.jboss.org/browse/JBIDE-20524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Blocker > Labels: upstream > Fix For: 4.3.0.CR1 > > > Upstream regression Mars 4.5.0 XULRunner [Bug 472956|https://bugs.eclipse.org/bugs/show_bug.cgi?id=472956] > Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20524) Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0)

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-20524: ----------------------------------- Summary: Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0) Key: JBIDE-20524 URL: https://issues.jboss.org/browse/JBIDE-20524 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core, xulrunner Affects Versions: 4.3.0.Beta2 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Priority: Blocker Fix For: 4.3.0.CR1 Upstream regression Mars 4.5.0 XULRunner [Bug 472956|http://atlassian.com]https://bugs.eclipse.org/bugs/show_bug.cgi?id... Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-482: ---------------------------------- [~nickboldt] - cool script - where can I find find.sh ? > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20520) Project tree item in New OpenShift Application wizard disappear after click on a template

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20520?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20520: ------------------------------------- the 2nd screenshot is the expected result. You shouldn't see the projects anymore in the viewer. See JBIDE-20477. > Project tree item in New OpenShift Application wizard disappear after click on a template > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20520 > URL: https://issues.jboss.org/browse/JBIDE-20520 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Attachments: after.png, before.png > > > Click on a template on the first wizard page In a New OpenShift Application wizard makes disappear the project tree item having the template. See following screenshots: > before click on a template > !before.png! > after click on a template > !after.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-480) JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final - update jbosstools/devstudio infrastructure

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-480?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-480: -------------------------------- Assignee: Paul Leacu Resolution: Done https://github.com/jbdevstudio/jbdevstudio-website/commit/da3eda2dc334af5... https://github.com/jbosstools/jbosstools-website/commit/97d7002a7aacdd7ac... > JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final - update jbosstools/devstudio infrastructure > ------------------------------------------------------------------------------- > > Key: JBTIS-480 > URL: https://issues.jboss.org/browse/JBTIS-480 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.3.GA, 4.2.3.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.3.GA, 4.2.3.Final > > > Update jbosstools-download.jboss.org and jbdevstudio-website with 4.2.3.Final/ 8.0.3.GA distribution infrastructure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20519) Internal model fails when multiple instances of Studio are opened

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20519?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20519: --------------------------------------------- why are these not stored in eclipse workspace which are only possible to load in one eclipse instance at the time ? > Internal model fails when multiple instances of Studio are opened > ----------------------------------------------------------------- > > Key: JBIDE-20519 > URL: https://issues.jboss.org/browse/JBIDE-20519 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > To save memory, the internal model stores long text in temporal files with prefix efs_, created in delete-on-exit mode. Since Studio may crash or be killed in the task manager, these files may remain for ever, and to prevent it, model plugin removes files with prefix efs_ during normal exit. > That produces the following problem: > 1. Open Studio in a new workspace, create a jsf project and build it. > 2. Open second instance of Studio in another new workspace, create exactly the same jsf project and build it. > 3. Close the second instance of Studio. > 4. In the first instance of Studio, try clean/build. > Failure: Logged messages like > java.lang.IllegalStateException: Cannot read /tmp/efs_2500225045660665987.sp.txt for object -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20447) 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20447?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20447: --------------------------------------------- is this not more reliably fixed on jenkins side where we know the node name and can pass explicit flag/profile in based on that ? > 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component > ------------------------------------------------------------------ > > Key: JBIDE-20447 > URL: https://issues.jboss.org/browse/JBIDE-20447 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Labels: testfailure > Fix For: 4.3.0.CR1 > > > *2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.0.CR1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowserOrLink{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowserOrLink} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.268</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowserOrLink(BrowserUtilTest.java:51) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowserOrLink</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowser{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowser} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.0030</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowser</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20523) Visual Page Editor Preferences don't work (changes are not persisted)

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-20523: ----------------------------------- Summary: Visual Page Editor Preferences don't work (changes are not persisted) Key: JBIDE-20523 URL: https://issues.jboss.org/browse/JBIDE-20523 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core Affects Versions: 4.3.0.Beta2 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Priority: Critical Fix For: 4.3.0.CR1 Steps to reproduce: 1) Open JBoss Tools -> Web -> Editors -> Visual Page Editor 2) Change some preferences 3) Press "OK" button 4) ERROR -> Error dialog will be displayed / preferences were not persisted -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 August 2015