[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Max Rydahl Andersen updated JBDS-1241: -------------------------------------- Priority: Critical (was: Major) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Max Rydahl Andersen commented on JBDS-1241: ------------------------------------------- We should have it outlined for M2 and prefereably implemented for Beta/CR1 Assigning to Denis right now since he will be working on Eclipse product definition -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Work on JBDS-1241 started by Denis Golovin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Denis Golovin updated JBDS-1241: -------------------------------- Description: Simplest way to replicate: 1. Install JBDS 3.0.0.RC1 which is included Eclipse 3.5.1 2. Strat JBDS and Select Help->Check for Updates ... 3. Install Eclipse 3.5.2 related updates 4. Restart JBDS after this issue is fixed restart should show JBDS splash, but for now it is changed for Eclipse one. Two problems should be solved here: 1. Keep JBDS product running by default after update 2. Keep JBDS Splash screen First problem solution is altering eclipse.ini during build. -product parameter should be added to eclipse.ini and that overrides eclipse.product from configuration/config.ini nfile. -product com.jboss.jbds.product.product Second is probably unsolvable until eclipse 3.7 is out. According https://bugs.eclipse.org/bugs/show_bug.cgi?id=274127. Every update at least for updates between 3.5 service releases leads to configuration/config.in and eclipse.ini modification. It reverts product related properties in config.ini to default ones eclipse.product=org.eclipse.sdk.ide osgi.splashPath=platform\:/base/plugins/org.eclipse.platform and always adds/replace -showSplash option in config.ini -showsplash org.eclipse.platform Combination of these changes lead to JBDS restart as default eclipse installation with about dialog and splash looking like regular eclipse installation. was: Simplest way to repcate: 1. Install JBDS 3.0.0.RC1 which is included Eclipse 3.5.1 2. Strat JBDS and Select Help->Check for Updates ... 3. Install Eclipse 3.5.2 related updates 4. Restart JBDS after this issue is fixed restart should show JBDS splash, but for now it is changed for Eclipse one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Work on JBDS-1241 stopped by Denis Golovin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Max Andersen commented on JBDS-1241: ------------------------------------ and aren't these p2 info's only being activated because JBDS 3 used the eclipse product definition and not our own ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1241?page=com.atlassian.jira.plugin.sy... ] Denis Golovin updated JBDS-1241: -------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta2) all isues related to new p2 enabled product build are moved to 4.0.0.CR1 -- 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-1241?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-1241. --------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira