January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3331: ------------------------------------ Setting SWT_GTK3=0 had no effect on the exceptions raised. > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3210) create a JBDS Central feature which includes only JBDS Central branding plugin

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3210?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-3210: ---------------------------------- [~nickboldt] +1 It appears the JBDSIS feature wrappers will do the trick. We can always reopen if we find otherwise. > create a JBDS Central feature which includes only JBDS Central branding plugin > ------------------------------------------------------------------------------ > > Key: JBDS-3210 > URL: https://issues.jboss.org/browse/JBDS-3210 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Purpose: > Provide a single feature which includes both JBoss Central (pulled from JBoss Tools, minus its "community" plugin, org.jboss.tools.community.central) and the JBDS Central branding plugin, com.jboss.devstudio.core.central. > Reason: > This will allow us to create Marketplace installs for things like JBDS Fuse Tooling which include ONLY the Fuse features + the bare bones of Central, without having all of JBDS come along for the ride. Without this, we can create a JBoss Tools-branded Fuse entry in the Marketplace, or a JBDS-branded Fuse entry in the Marketplace [which includes all of JBDS]. We want a JBDS-branded Fuse entry, which only includes the bare bones, not ALL the JBDS stuff. > Technical problems: > * Marketplace can only install features, not individual plugins > * Today, the only way to install JBDS Central via Marketplace is to include the com.jboss.devstudio.core.feature, which includes the com.jboss.devstudio.core.central branding plugin. But doing so installs ALL of JBDS, too. > Solution: > 1. Create a com.jboss.devstudio.core.central.feature which includes: > * com.jboss.devstudio.core.central > * org.jboss.tools.central > 2. Optionally, could also include these plugins: > * com.jboss.devstudio.core.project.examples > * com.jboss.devstudio.core.usage.branding -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-15332: --------------------------------------- This jira is about {quote}skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism{quote} so it goes right to this line probably https://github.com/dgolovin/jbosstools-build/blob/master/parent/pom.xml#L391 > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3319: ------------------------------------- Look at https://github.com/dgolovin/jbdevstudio-product/blob/master/installer/src.... You should replace 420 for 660 here. IzPack should to take care of everything else. > JBDS 9.0 installer underreports space requirement by 225 - 250MB > ---------------------------------------------------------------- > > Key: JBDS-3319 > URL: https://issues.jboss.org/browse/JBDS-3319 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.2.GA > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required: > Disk Space: > Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB > The actual install uses this much: > du -sh installdir/ > 822M installdir/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3210) create a JBDS Central feature which includes only JBDS Central branding plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3210?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3210: ---------------------------------- Since JBDS needs a core.feature to perform the BYOE / installer install, and since the pieces of the JBDS IS install all need their own top-level feature wrappers, we don't really need this new feature after all... all it would do is marginally simplify the handful of JBDS IS features so that they could include/require this feature, rather than a collection of plugins. [~pleacu] Do you still want this feature? Seems like we've successfully worked around the need for it in JBDS IS 8. > create a JBDS Central feature which includes only JBDS Central branding plugin > ------------------------------------------------------------------------------ > > Key: JBDS-3210 > URL: https://issues.jboss.org/browse/JBDS-3210 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Purpose: > Provide a single feature which includes both JBoss Central (pulled from JBoss Tools, minus its "community" plugin, org.jboss.tools.community.central) and the JBDS Central branding plugin, com.jboss.devstudio.core.central. > Reason: > This will allow us to create Marketplace installs for things like JBDS Fuse Tooling which include ONLY the Fuse features + the bare bones of Central, without having all of JBDS come along for the ride. Without this, we can create a JBoss Tools-branded Fuse entry in the Marketplace, or a JBDS-branded Fuse entry in the Marketplace [which includes all of JBDS]. We want a JBDS-branded Fuse entry, which only includes the bare bones, not ALL the JBDS stuff. > Technical problems: > * Marketplace can only install features, not individual plugins > * Today, the only way to install JBDS Central via Marketplace is to include the com.jboss.devstudio.core.feature, which includes the com.jboss.devstudio.core.central branding plugin. But doing so installs ALL of JBDS, too. > Solution: > 1. Create a com.jboss.devstudio.core.central.feature which includes: > * com.jboss.devstudio.core.central > * org.jboss.tools.central > 2. Optionally, could also include these plugins: > * com.jboss.devstudio.core.project.examples > * com.jboss.devstudio.core.usage.branding -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-382) BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-382?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-382: ---------------------------------- Does BPMN2 modeler need to be on the JBDS IS release site? Why can't it be ONLY on the JBDS IS EA site? If there is a .Final version of something in JBDS IS release site that depends on this pre-release version of BPMN2 modeler, then yes, it's OK to have it as a hidden dependency in the target platform, because there's no other way to get it there. If, however, there's nothing .Final that requires/depends on this pre-release BPMN2 stuff, then it should be moved exclusively to the JBDS IS EA site, so as not to besmirch the quality of the Final/GA JBDS IS release site/zip. > BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site > ---------------------------------------------------- > > Key: JBTIS-382 > URL: https://issues.jboss.org/browse/JBTIS-382 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.CR1 > Environment: 8.0.2.GA + JBDS-IS 8.0.0.CR1 (no early access) > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: tp1.png, tp2.png > > > BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site where should not be. > By default this feature is not visible when you install integration stack from the update site. But when you uncheck "Group item by category" the feature is available and can be installed. Moreover, the old version of BPMN2 modeler is installed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3331 at 1/26/15 11:44 AM: ------------------------------------------------------------ Workaround [use SWT_GTK3=0] and related upstream problems reported here: JBIDE-16290 and JBIDE-18667. Looks like the upstream problems won't be fixed in Luna SR2. :( was (Author: nickboldt): Workarounds and related upstream problems reported here: JBIDE-16290 and JBIDE-18667 > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18667?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18667: ------------------------------------ None of the above Eclipse bugs are fixed as of Jan 26, with Luna SR2 RC1 now available. Signs point to "Won't Fix", especially since none have a Target Milestone set, nor have they been touched since 2014-08-26 or earlier. > Fixing SWT issues in Luna SR2 > ----------------------------- > > Key: JBIDE-18667 > URL: https://issues.jboss.org/browse/JBIDE-18667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Jiri Peterka > Fix For: 4.2.3.Final > > > Unresolved issues in Luna SR1 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431421 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431423 > https://issues.jboss.org/browse/JBIDE-16879 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=431425 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=434898 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-382) BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-382?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-382: ---------------------------------- Is it actually an issue if we expose potentially non .Final features from the JBTIS target platform when a user must first uncategorize the installation components and then select the features they want to install? Additionally these features will work with any of the .Final components (see attachments). [~nickboldt] WDYT? > BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site > ---------------------------------------------------- > > Key: JBTIS-382 > URL: https://issues.jboss.org/browse/JBTIS-382 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.CR1 > Environment: 8.0.2.GA + JBDS-IS 8.0.0.CR1 (no early access) > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: tp1.png, tp2.png > > > BPMN2 modeler is available at JBDS-IS 8.0.0.CR1 site where should not be. > By default this feature is not visible when you install integration stack from the update site. But when you uncheck "Group item by category" the feature is available and can be installed. Moreover, the old version of BPMN2 modeler is installed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3331 at 1/26/15 11:39 AM: -------------------------------------------------------------- Performed these steps on RHEL 6.6: Configured access to Red Hat Developer Toolset sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-source-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-source-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-rpms Installed Red Hat Developer Toolset sudo yum install devtoolset-3 Opened Eclipse, installed (Abridged) JBoss Tools 4.2.2 from: http://download.jboss.org/jbosstools/updates/stable/luna/ (Welcome screen is blank/white) Restarted Eclipse, Attempted to Install Kitchensink web quickstart Exception raised in trying to download/install EAP runtime: Unhandled event loop exception No more handles (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-gtk-4427 in java.library.path no swt-xulrunner-gtk in java.library.path Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4427.so Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so ) (Installed EAP 6.2 outside of IDE and continued) Maven repo updated correctly, app builds. Installed JBoss helloworld app Builds cleanly, deploys, app can be accessed fron client See attached screenshots and eclipse log file. was (Author: ldimaggio): Performed these steps on RHEL 6.5: Configured access to Red Hat Developer Toolset sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-source-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-source-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-beta-debug-rpms sudo subscription-manager repos --enable rhel-workstation-rhscl-6-rpms Installed Red Hat Developer Toolset sudo yum install devtoolset-3 Opened Eclipse, installed (Abridged) JBoss Tools 4.2.2 from: http://download.jboss.org/jbosstools/updates/stable/luna/ (Welcome screen is blank/white) Restarted Eclipse, Attempted to Install Kitchensink web quickstart Exception raised in trying to download/install EAP runtime: Unhandled event loop exception No more handles (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-gtk-4427 in java.library.path no swt-xulrunner-gtk in java.library.path Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4427.so Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so ) (Installed EAP 6.2 outside of IDE and continued) Maven repo updated correctly, app builds. Installed JBoss helloworld app Builds cleanly, deploys, app can be accessed fron client See attached screenshots and eclipse log file. > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015