[jbosstools-issues] [JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3652 at 4/13/16 10:29 AM: ------------------------------------------------------------ It might be faster to simply: unzip jbds.zip -d c:\devplatform vs. java -jar jbds.jar install.xml because the installer process has to unpack the jar, then unpack some of the jars in the jar (features + some plugins), then generate metadata & other files. So we could do all the installation up front when CREATING the devplatform installer, then simply zip up the results and embed THAT in the devplatform installer. So we'd still be using the installer the same way a normal user would, but we'd be then MOVING that install from a temp location into the dp installer and then out onto the user's disk. PROBABLY would work fine assuming no network drives, user permission issues, nothing installed into ~/.eclipse, and no spaces-in-paths issues. -- But to your point, it might be better to not precache that because a user might choose to install onto d:\dp or a network drive, in which case SOME of the installation process might end up in ~/.eclipse rather than in that user's d:\dp folder. So... yeah, I'd say we're better off letting the JBDS installation happen live, rather than pre-canning it and hoping it all goes to plan. -- I vote this should be a "WONTFIX". was (Author: nickboldt): It might be faster to simply: unzip jbds.zip -d c:\devplatform vs. java -jar jbds.jar install.xml because the installer process has to unpack the jar, then unpack some of the jars in the jar (features + some plugins), then generate metadata & other files. So we could do all the installation up front when CREATING the devplatform installer, then simply zip up the results and embed THAT in the devplatform installer. So we'd still be using the installer the same way a normal user would, but we'd be then MOVING that install from a temp location into the dp installer and then out onto the user's disk. PROBABLY would work fine assuming no network drives, user permission issues, nothing installed into ~/.eclipse, and no spaces-in-paths issues. -- But to your point, it might be better to not precache that because a user might choose to install onto d:\dp or a network drive, in which case SOME of the installation process might end up in ~/.eclipse rather than in that user's d:\dp folder. So... yeah, I'd say we're better off letting the JBDS installation happen live, rather than pre-canning it and hoping it all goes to plan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)