[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBDS-1599) Dependency on Gnome not documented?

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596448#comment-12596448 ] 

Nick Boldt edited comment on JBDS-1599 at 4/19/11 11:00 AM:
------------------------------------------------------------

A few things ;) It's the first time I've bumped into someone expecting eclipse or any UI app to run without having Gnome or KDE or something similar started - that said, I agree that it should be explicitly stated if the error from Eclipse on startup on a Linux system that does not have GTK gives such a useless error message.

Note, running Gnome actually should not be necessary - KDE is fine too.

About the installers then there are many aspects in this.

The 10 installers - currently we have -8- 10 of them; (Windows 32-bit, Linux-32, Linux-64, OSX Cocoa, -OSX Carbon-, OSX Cocoa 64-bit) * (with or without EAP). Adding a RPM as a wrapper around it would add two possibly four (if we need both 32 and 64 bit rpms): (RHEL-32, RHEL-64) * (with or without eap)

Bundled vs non-bundled EAP: We bundle EAP so we know it is configured out of the box to be used as a development server - the one coming in with EAP RPM's and other default installs are locked down and thus you would have that problem to fight with too.

Little work vs Big work: This is not a "little work" - it requires development, QE, maintenance and documentation. 

Real RPM vs Wrapping RPM: The set of dependencies to run JBDS is not available on RHEL; we would need to go create those and that is a *massive* undertaking. That + the fact EAP used for production installs via RPM arent configured for development, is why we want to create the "wrapping" RPM. 



      was (Author: maxandersen):
    A few things ;) It's the first time I've bumped into someone expecting eclipse or any UI app to run without having Gnome or KDE or something similar started - that said, I agree that it should be explicitly stated if the error from Eclipse on startup on a Linux system that does not have GTK gives such a useless error message.

Note, running Gnome actually should not be necessary - KDE is fine too.

About the installers then there are many aspects in this.

The 10 installers - currently we have 8 of them; (Windows 32-bit, Linux-32, Linux-64, OSX Cocoa, OSX Carbon) * (with or without EAP). Adding a RPM as a wrapper around it would add two possibly four (if we need both 32 and 64 bit rpms): (RHEL-32, RHEL-64) * (with or without eap)

Bundled vs non-bundled EAP: We bundle EAP so we know it is configured out of the box to be used as a development server - the one coming in with EAP RPM's and other default installs are locked down and thus you would have that problem to fight with too.

Little work vs Big work: This is not a "little work" - it requires development, QE, maintenance and documentation. 

Real RPM vs Wrapping RPM: The set of dependencies to run JBDS is not available on RHEL; we would need to go create those and that is a *massive* undertaking. That + the fact EAP used for production installs via RPM arent configured for development, is why we want to create the "wrapping" RPM. 


  
> Dependency on Gnome not documented?
> -----------------------------------
>
>                 Key: JBDS-1599
>                 URL: https://issues.jboss.org/browse/JBDS-1599
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: Doc - RHDS GSG
>         Environment: RHEL6 64bit. OpenJDK. Minimum install:
> @Base
> @Development Tools
> @Java
> @Java Development
> @X Windows
>            Reporter: Peter Larsen
>              Labels: gnome,, jbds,
>             Fix For: 4.0.0.GA
>
>
> When loading JBDS without gnome running, the following error/issue is reported:
> GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: /bin/dbus-launch terminated abnormally without any error message)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira