[ https://jira.jboss.org/jira/browse/JBDS-735?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBDS-735: --------------------------------- Please provide more detail / example as to what was done / should be done instead. I need a more complete spec than "make it good." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-735?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBDS-735: ---------------------------------- In the past eclipse.ini looked something like this: -showsplash org.eclipse.platform -vmargs -Xms256m -Xmx512m -XX:MaxPermSize=512m Now eclipse.ini looks something like this: -startup plugins/org.eclipse.equinox.launcher_1.0.200.v20090429-1630.jar --launcher.library plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.200.v20090306-1900 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 512m -vmargs -Xms256m -Xmx512m I know that hte JBDS build often changed the eclipse.ini slightly for any number of reasons including adding customizing the memory args (or anything else). This JIRA was to make sure that the eclipse.ini customizations did not clobber the new required parts of eclipse.ini such as the startup plugin jar, or hte launcher.library jar. I had discovered this bug because my quick-install script for a new eclipse installation similarly coppied a custom eclipse.ini into the unzipped eclipse installation, however I realized I could not get any of my new installations to actually run. it took me a few hours to figure out the eclipse.ini had been clobbered in a way that made the installation unable to start up. After mentioning this, I was told to make a JIRA for it to make sure the official build system did not suffer from the same problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBDS-735?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBDS-735. ------------------------------------ Resolution: Duplicate Issue for 2.1.0 it is ok for now since the version properties are hardcoded and now updated. For 3.0 JBDS-723 and JBDS-729 captures this issue better and aare blocker/critical. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira