[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1718: -------------------------------- Description: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all{noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all{noformat} was: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. -- 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-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1718: -------------------------------- Description: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 482798 ms. {noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 4827 ms. {noformat} was: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 482798 ms. {noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 4827 ms. {noformat} -- 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-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1718: -------------------------------- Description: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 482798 ms. {noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 4827 ms. {noformat} Problems to solve: * How to track p2 director installation progress * Is there a way to install it without unpacking p2repo to disk first (as an option can try to pack p2 repo as a library and references it as file://installer.jar/p2repo!/) * How to install TestNG which is part of JBDS Extra * ??? was: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 482798 ms. {noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 4827 ms. {noformat} Problems to solve: * How to track p2 director installation progress * Is there a way to install it without unpacking p2repo to disk first (as an option can try to pack p2 repo as a library and references it as file://installer.jar/p2repo!/) * ??? -- 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-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1718: -------------------------------- Description: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 482798 ms. {noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 4827 ms. {noformat} Problems to solve: * How to track p2 director installation progress * Is there a way to install it without unpacking p2repo to disk first (as an option can try to pack p2 repo as a library and references it as file://installer.jar/p2repo!/) * How to install TestNG which is part of JBDS Extra * Would be good to have build for p2director app instead of using one from buckminister * ??? Possible installation implementation: 1. Use director app and install it out of p2repo 2. Implements installer step based on :pserver:anonymous@dev.eclipse.org:/cvsroot/rt:org.eclipse.equinox/p2/bundles/org.eclipse.equinox.p2.installer was: Installer should utilize p2director and JBDS p2 repository created bt product build. That let us to have one installer for all platforms instead of five. Size of installer is going to be more because of multi-platform bits inside p2repo and p2Director application included. Installer based on IzPack has to extract p2repo first and then materialize JBDS using p2 director application. Buckminister p2 director available from http://www.eclipse.org/downloads/download.php?file=/tools/buckminster/pro... Literally now it can be installed like this: {noformat}director -r http://update-site-host/updates/nightly/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 482798 ms. {noformat} or for local p2 repo archive {noformat}director -r file:///path-to-local-update/jbdevstudio-product-Update-4.1.0.v201107141200R-H631-CR3.zip!/ -d /install/target/directory -p jbds -i com.jboss.jbds.all -profileProperties org.eclipse.update.install.features=true Installing com.jboss.jbds.all 4.1.0.201107071838. Operation completed in 4827 ms. {noformat} Problems to solve: * How to track p2 director installation progress * Is there a way to install it without unpacking p2repo to disk first (as an option can try to pack p2 repo as a library and references it as file://installer.jar/p2repo!/) * How to install TestNG which is part of JBDS Extra * Would be good to have build for p2director app instead of using one from buckminister * ??? -- 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-1718?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-1718: ------------------------------------------- Denis - what is the status here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-1718 at 12/6/11 8:59 PM: -------------------------------------------------------------- Have it working locally and tested for windows-64, Mac -d32 and -d64, linux gtk-x86_64. So far problems I have solved: 1. Showing progress for p2-director 2. Spaces in jvm location Leftover issues: 1. Cancel installation when p2-director is running 2. Spaces in installation location (under linux) 3. Error processing when something goes wrong when running p2director 4. Update build results page 5. Progress bar is not working for windows was (Author: dgolovin): Have it working locally and tested for windows-64, Mac -d32 and -d64, linux gtk-x86_64. So far problems I have solved: 1. Showing progress for p2-director 2. Spaces in jvm location Leftover issues: 1. Cancel installation when p2-director is running 2. Spaces in installation location (under linux) 3. Error processing when something goes wrong when running p2director 4. Update build results page -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-1718: ------------------------------------- I know, I'm going to fix progress and build results today -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1718: ---------------------------------- Revision 8323 by dgolovin has caused trunk build to fail. {code} build-platform-installer: [echo] Building installer for macosx-cocoa platform... [echo] path to macosx.cocoa.x86 platform zip /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/jbds-all-package/jbdevstudio-5.0.0.v201112080535N-H855-Beta1-macosx.cocoa.x86.zip init-properties: buildcustompanels: [echo] Building panels ... [echo] Build properties written to /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/../../jbds-echoproperties.txt [unjar] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/IzPack-4.3.4/lib/standalone-compiler.jar into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/izpack-panels [unjar] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/IzPack-4.3.4/lib/installer.jar into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/classes [unjar] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/izpack-panels/bin/panels/HTMLInfoPanel.jar into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/classes [unjar] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/IzPack-4.3.4/bin/panels/InstallationGroupPanel.jar into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/classes [unjar] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/IzPack-4.3.4/lib/installer.jar into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/classes prepare-distribution-properties: prepare-jbosseap: [mkdir] Created dir: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/distribution/jboss-eap-5.1 [unzip] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/requirements/jbeap-5.0.0/jboss-eap-noauth-5.1.1.zip into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/distribution prepare-jbds: prepare-jbds-regular: [mkdir] Created dir: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/distribution/studio/temp [unzip] Expanding: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/jbds-all-package/jbdevstudio-product-5.0.0.v201112080535N-H855-Beta1-macosx.cocoa.x86.zip into /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/distribution BUILD FAILED /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/buildNightly.xml:15: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/build.xml:70: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/build.xml:41: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:131: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:741: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/product/buildInstallerPde.xml:47: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/product/buildInstallerPde.xml:49: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/org.jboss.ide.eclipse.releng/builders/product/buildInstallerPde.xml:113: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build-pde.xml:226: The following error occurred while executing this line: /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build-pde.xml:244: Warning: Could not find file /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/5.0.0.Beta1/201112080535/installer/build/distribution/studio/jbdevstudio.app to copy. Total time: 86 minutes 40 seconds {code} http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-5.0_trunk.... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1718: -------------------------------- Attachment: screenshot20111208101308.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-1718: ------------------------------------- It always add -vm into jbdevstudio.ini file. On Mac it also uses -vmargs -d32/64 (based on sun.arch.data.model system property) during installing jbds out of update site. So on mac if you want VPE just use {noformat}java -d32 <installer-name>.jar{noformat} that will switch studio into -d32 mode. To verify that fast without creating project use CSS Preview. For JBDS installed on mac like {noformat}java <installer-name>.jar{noformat} You'll see empty view with text message. For installatiion in 32 bit mode {noformat}java -d32 <installer-name>.jar{noformat} You'll see preview with text "Double click here to ...". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-1718: ------------------------------------- Universal installer is not working for windows right now. Yahor, just helped me to find the reason. I'm testing it on trunk build (because branch build is broken) and will merge it to branch after testing on all three supported platforms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-1718: ---------------------------------- However, seems the macosx installer is now broken. Related issue, or Jenkins problem? {code} /home/hudson/hudson_workspace/workspace/devstudio-5.0_stable_branch.product/jbds-build/5.0.0.M5/201112121820/jbds-all-package/package.org.eclipse.pde.build.container.feature.macosx.cocoa.x86_64.xml:1399: Unable to delete directory /home/hudson/hudson_workspace/workspace/devstudio-5.0_stable_branch.product/jbds-build/5.0.0.M5/201112121820/jbds-all-package/tmp {code} https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indi... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.... ] Jiri Peterka closed JBDS-1718. ------------------------------ Universal installer works, verified JBDS build 5.0.0.M5a, H62. Specific issues will be tracked separately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira