January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3275: ---------------------------------------- Makes sense [~fbricon]. It will also be odd to see "Your application can run on: JBoss EAP and WildFly" by now. I'll update DESIGN-659 to ask for a "WildFly only" version of the banner. > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-358) Use wrapper features to simplify the install and clean up the Marketplace UI?

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-358?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-358: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/commit/f7a31a5... Generate feature.xml from plugin.xml. > Use wrapper features to simplify the install and clean up the Marketplace UI? > ----------------------------------------------------------------------------- > > Key: JBTIS-358 > URL: https://issues.jboss.org/browse/JBTIS-358 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 7.0.3.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.GA-JBDSIS > > Attachments: is-marketplace1.png, is-marketplace2.png > > > For 7.1.0, could consider having wrapper features to simplify the install and clean up the Marketplace UI. Doing so would mean instead of a laundry list of features in the UI, we could list only 3 features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-161. ---------------------------- Resolution: Done Fully tested (JBDSIS 7.0.3.GA) with no conflicting issues using SpringIDE 3.2 jars. > Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? > -------------------------------------------------------------------------- > > Key: JBTIS-161 > URL: https://issues.jboss.org/browse/JBTIS-161 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.2 > Reporter: Nick Boldt > Assignee: Paul Leacu > > The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. > [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... > However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). > Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3275: ----------------------------------- The problem is there's no JavaEE 7 compatible EAP version, yet. So Showing both EAP and WF on the same banner would be awkward IMO. I would personally stick with a WF only banner for the time being, update it to a dual brand once EAP 7 is out. [~pmuir], any thoughts? > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3275: ---------------------------------------- I opened DESIGN-659 to [~james.cobb] team because I don't think using http://static.jboss.org/wildfly/images/wildfly-banner-1180px.png will produce a good result. I also also opened WFLY-4224 for me because it still have a lot of references to JBossAS. > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18995: ---------------------------------------- Ok, so +1 to merge those PRs and to update the file on download.jboss.org. > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.2.Final > > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18995: ------------------------------- Fix Version/s: 4.2.2.Final > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.2.Final > > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-374) Unknown category 'org.jboss.tools.central.discovery.a.web' when installing from central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-374?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-374. ------------------------------ Fix Version/s: 8.0.0.CR1 Resolution: Done Corrected the discovery directory XML generation script to handle multiple entry URLs from the upstream core > Unknown category 'org.jboss.tools.central.discovery.a.web' when installing from central > --------------------------------------------------------------------------------------- > > Key: JBTIS-374 > URL: https://issues.jboss.org/browse/JBTIS-374 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta2 > Environment: JBDS 8.0.1.GA + JBDS-IS 8.0.0.Beta2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 8.0.0.CR1 > > > The following errors occur when we want to install JBDS-IS from JBoss Central > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2014-12-16 08:23:00.010 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in com.jboss.jbds.central.discovery.earlyaccess_8.0.0.Final_v20141017_1053_B366.jar_8432436156156296317.jar > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2014-12-16 08:23:00.023 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'org.jboss.tools.arquillian' declared in com.jboss.jbds.central.discovery.earlyaccess_8.0.0.Final_v20141017_1053_B366.jar_8432436156156296317.jar > This occurs only in error log and has no impact on the installation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18995) Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18995: ------------------------------------ IIRC, Arquillian is only EA in JBDS, hence my PRs. We can't rebuild 4.2.1, but we could change this in 4.2.2, if required. I don't think it's necessary to rebuild anything in 4.2.x. I believe we just need to update the earlyaccess.properties file used by JBT in the stable/ folder. > Early Access features can be installed from JBoss Tools p2 repository even if 'Enable Early Access' is disabled in Central > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18995 > URL: https://issues.jboss.org/browse/JBIDE-18995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.Final > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Minor > Attachments: ea-disabled.png, ea-installed.png > > > I noticed central has "(Early Access Installed)" sign in after I installed everything from JBos Tools stable p2 repository. > !ea-installed.png! > "Enable Early Access" checkbox is not set by default in Central Editor > !ea-disabled.png! > This means I bypassed warning dialog in this scenario. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18979) Unable to run CordovaSim with Fedora 21 KDE

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18979?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-18979: ------------------------------------ I was able to run browsersim on F21 (upgraded from F20) {noformat} % uname -r 3.17.4-302.fc21.x86_64 % java -version openjdk version "1.8.0_25" OpenJDK Runtime Environment (build 1.8.0_25-b18) OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode) % rpm -qa | grep webkitgtk webkitgtk-2.4.7-1.fc21.x86_64 webkitgtk3-2.4.7-1.fc21.x86_64 webkitgtk4-2.6.4-1.fc21.x86_64 {noformat} It was working both with GTK2 and GTK3. > Unable to run CordovaSim with Fedora 21 KDE > ------------------------------------------- > > Key: JBIDE-18979 > URL: https://issues.jboss.org/browse/JBIDE-18979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.2.1.Final > Environment: JBDS 8.0.1.CR1-v20141207-0100-B352, Java Oracle 1.8 > Fedora 21 KDE 64 bit > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Alpha1 > > Attachments: fedora.png, webkit.png > > > 1. Run default Hybrid Mobile app with CordovaSim > {noformat} > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:000] Computer model: Not available > [000:000] Browser XEmbed support present: 1 > [000:000] Browser toolkit is Gtk2. > [000:003] Using Gtk2 toolkit > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:001] Computer model: Not available > [000:497] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:497] No bp log location saved, using default. > [000:497] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:497] Computer model: Not available > [000:498] Browser XEmbed support present: 1 > [000:498] Browser toolkit is Gtk2. > [000:498] Using Gtk2 toolkit > [000:003] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:003] No bp log location saved, using default. > [000:004] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:004] Computer model: Not available > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000370a80c42b, pid=13580, tid=140558422947584 > # > # JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0xc42b] > # > # 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/vpakan/hs_err_pid13580.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015