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

Nick Boldt (JIRA) jira-events at lists.jboss.org
Mon Apr 18 15:31:33 EDT 2011


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

Nick Boldt edited comment on JBDS-1599 at 4/18/11 3:30 PM:
-----------------------------------------------------------

Notice how there's a "gtk" in JBDS installer jar filename? That's not accidental. Eclipse on linux needs GTK. Sorta like Eclipse on Mac requires Cocoa (or previously Carbon). 

For extreme details on what Eclipse (and therefore JBDS) needs, see:

http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/linPlatform.php#PlatformRuntime (32- and 64-bit, GTK 2 only)
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/macPlatform.php#PlatformRuntime (32- and 64-bit, Cocoa only)
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/winPlatform.php#PlatformRuntime (32-bit Windows only)
or
http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments

As to RPM packaging, no, that wouldn't make things easier since we'd then need 14 installers, not 10. If we get to the point where we have two multi-platform installers (one w/ EAP, one without), then yes, wrapping RPM around that is not unreasonable. But adding 40% more packages (and disk footprint on servers for building/staging/publishing) is not reasonable at this time.

      was (Author: nickboldt):
    Notice how there's a "gtk" in JBDS installer jar filename? That's not accidental. Eclipse on linux needs GTK. Sorta like Eclipse on Mac requires Cocoa (or previously Carbon). 

For extreme details on what Eclipse (and therefore JBDS) needs, see:

http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/linPlatform.php#PlatformRuntime (32- and 64-bit, GTK 2 only)
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/macPlatform.php#PlatformRuntime (32- and 64-bit, Cocoa only)
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/winPlatform.php#PlatformRuntime (32-bit Windows only)

As to RPM packaging, no, that wouldn't make things easier since we'd then need 14 installers, not 10. If we get to the point where we have two multi-platform installers (one w/ EAP, one without), then yes, wrapping RPM around that is not unreasonable. But adding 40% more packages (and disk footprint on servers for building/staging/publishing) is not reasonable at this time.
  
> 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


More information about the jbosstools-issues mailing list