[ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1599: ------------------------------------------- Eclipse requires GTK to run afaik ? Is that what you are asking for being documented ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1599: ---------------------------------- 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/... (32- and 64-bit, GTK 2 only) http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (32- and 64-bit, Cocoa only) http://download.eclipse.org/eclipse/downloads/drops/R-3.6.2-201102101200/... (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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.... ] 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... 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1599?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1599: -------------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.M1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-188?page=com.atlassian.jira.plug... ] Isaac Rooskov updated TOOLSDOC-188: ----------------------------------- Fix Version/s: 3.2.1.Final Component/s: Getting Started Guide -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-188?page=com.atlassian.jira.plug... ] Martin Malina closed TOOLSDOC-188. ---------------------------------- Verified in http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Developer_Stud... . -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira