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

[Peter Larsen (JIRA)]

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

Peter Larsen commented on JBDS-1599:
------------------------------------

I also see a H93 long version numbers etc. If that's the only way we have the dependency documented, there's a problem..
http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html/Getting_Started_Guide/minimumrequirements.html

This link does not list _any_ packages needed on RHEL let alone GTK. I found no reference to gtk2 anywhere in the documentation on our site. 

You're going to have to help me understand what the issue is with RPM. 10 installers? Where? Since EAP should be a RPM based install already (I know it's not on RHEL6) that side is already taken care of. No need to make separate "jbds with/without EAP". That's the whole idea behind RPMs. Also, wrapping? I don't understand that either. And 40% more packages would replace the data in the existing distribution (zip/jar) which I don't see as adding any more space?   The only "bad side" I can see is that it needs to follow RHELs standards for software so just pushing things to $HOME is out of the question. So yes a little bit of work is needed - but help me understand why you see that as a large deal.

> 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