January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21584) Forge is missing default values in some wizards

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21584?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-21584: ------------------------------------ Environment: OS/X > Forge is missing default values in some wizards > ------------------------------------------------ > > Key: JBIDE-21584 > URL: https://issues.jboss.org/browse/JBIDE-21584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Environment: OS/X > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.3.1.CR1 > > Attachments: Screen Shot 2016-01-26 at 17.51.24.png, Screen Shot 2016-01-26 at 17.52.02.png > > > Forge is missing default values in some wizards . Please see the screenshots. It used to be prefilled with default values (in previous versions of forge). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21584) Forge is missing default values in some wizards

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21584?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-21584: ------------------------------------ Environment: OS X (was: OS/X) > Forge is missing default values in some wizards > ------------------------------------------------ > > Key: JBIDE-21584 > URL: https://issues.jboss.org/browse/JBIDE-21584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Environment: OS X > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.3.1.CR1 > > Attachments: Screen Shot 2016-01-26 at 17.51.24.png, Screen Shot 2016-01-26 at 17.52.02.png > > > Forge is missing default values in some wizards . Please see the screenshots. It used to be prefilled with default values (in previous versions of forge). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3587) Uninstalling features from central is misleading if the feature is required in JBDS

by Jan Richter (JIRA)

Jan Richter created JBDS-3587: --------------------------------- Summary: Uninstalling features from central is misleading if the feature is required in JBDS Key: JBDS-3587 URL: https://issues.jboss.org/browse/JBDS-3587 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central Affects Versions: 9.1.0.Beta2 Reporter: Jan Richter Since some features are both in default JBDS installation and in central, you can try uninstalling them from central. The uninstall wizard will show a strange cryptic message saying: {noformat}"#the selected feature# cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled".{noformat} That basically means nothing gets uninstalled, but it still requires a restart just for good measure. The question is - Can it either be more clear that you can't just uninstall those features using central, or just allow it? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3583: ------------------------------------- [~dgolovin], ok, but now I'm confused. (I just checked and it's not fixed in JBDS 9.1.0.Beta2.) I thought SR2 is now Mars.2, but apparently there is now Mars.1 R, SR1, SR2, Mars.2 R, SR1, SR2? That's new for me. Is Mars.1 SR2 released before JBDS 9.1.0.CR1? > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21298. --------------------------------- All of the recent builds are blue here: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m... Closing. > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component > ---------------------------------------------------------------------- > > Key: JBIDE-21298 > URL: https://issues.jboss.org/browse/JBIDE-21298 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Critical > Labels: testfailure > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m... > # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds) > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths} > <case> > <age>5</age> > <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className> > <duration>0.0050</duration> > <errorDetails>/qa/services/hudson/jboss-runtimes > expected:<0> but was:<1></errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes > expected:<0> but was:<1> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:234) > at junit.framework.TestCase.assertEquals(TestCase.java:401) > at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73) > </errorStackTrace> > <failedSince>58</failedSince> > <name>testLoadSaveRuntimePaths</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21470) Use MessageDialog instead of MessageBox in ZombieProcessPrompter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21470?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21470: --------------------------------------- [~rhopp], can you verify that this is indeed fixed now? > Use MessageDialog instead of MessageBox in ZombieProcessPrompter > ---------------------------------------------------------------- > > Key: JBIDE-21470 > URL: https://issues.jboss.org/browse/JBIDE-21470 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.1.Beta1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta2 > > > Our integration tests sometimes get stuck on this MessageBox as it creates native window which RedDeer nor SWTBot can access. Using MessageDialog enable us to handle it within our integration tests and as a bonus it matches eclipse look&feel better (imo). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-3586: ----------------------------------------- I got the same error even if I tried to install Graphiti into Eclipse Mars for JEE Developers. I have also reported the issue in eclipse bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=486638 > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21589) JBDS crash sometimes when opening Show in Console on a project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21589?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21589: ---------------------------------- Labels: openshift_v3 (was: ) > JBDS crash sometimes when opening Show in Console on a project > -------------------------------------------------------------- > > Key: JBIDE-21589 > URL: https://issues.jboss.org/browse/JBIDE-21589 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22 > openjdk 8.0_71-b15 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Attachments: log.txt > > > Crash log > {code} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032 > # > # JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15) > # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libwebkitgtk-3.0.so.0+0x47bcaf] > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /home/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {code} > For more thread dump see attached log.txt -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21589) JBDS crash sometimes when opening Show in Console on a project

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21589: ------------------------------------- Summary: JBDS crash sometimes when opening Show in Console on a project Key: JBIDE-21589 URL: https://issues.jboss.org/browse/JBIDE-21589 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Environment: Fedora 22 openjdk 8.0_71-b15 Reporter: Marián Labuda Priority: Critical Attachments: log.txt Crash log {code} # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032 # # JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15) # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libwebkitgtk-3.0.so.0+0x47bcaf] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # {code} For more thread dump see attached log.txt -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21406) Create and use Mars.2 RC1 target platform

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21406?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21406. --------------------------------- Closing. There is no verification for this JIRA really. But I trust that potential bugs will be spotted and reported as new JIRAs. > Create and use Mars.2 RC1 target platform > ----------------------------------------- > > Key: JBIDE-21406 > URL: https://issues.jboss.org/browse/JBIDE-21406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta2 > > Attachments: jbds-tp-p2diff-450-summary.txt, jbds-tp-p2diff-450.txt, jbds-tp-p2diff-summary.txt, jbds-tp-p2diff.txt, jbt-tp-p2diff-450-summary.txt, jbt-tp-p2diff-450.txt, jbt-tp-p2diff-summary.txt, jbt-tp-p2diff.txt, jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, p2diff.egit.summary.txt, rc1-rc1a.p2diff-filtered.txt, rc1-rc1a.p2diff.txt, too-many-osgi.png > > > Prepare new 4.52.x TPs to use Mars.2 bits. > https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M... > First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day). > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build > * update install/matrix jobs to use new Eclipse JEE/platform binary > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 2016