[jbosstools-issues] [JBoss JIRA] (JBDS-1718) One installer for all supported platforms

[Martin Malina (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649579#comment-12649579 ] 

Martin Malina commented on JBDS-1718:
-------------------------------------

I can see another issue not listed here yet:

Sometimes there is more than 1 platform suitable for installation. The user has no way to choose what arch is installed. Typical example: Mac OS X Lion - normally I would probably install the 32bit version but the universal installer automatically installs the 64bit version. Both are supported on Mac, but the 64bit version lacks support for VPE Editor.

So it would be nice if in such cases the user could choose which of those two to install.
                
> One installer for all supported platforms
> -----------------------------------------
>
>                 Key: JBDS-1718
>                 URL: https://issues.jboss.org/browse/JBDS-1718
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: installer
>    Affects Versions: 5.0.0.M5
>            Reporter: Denis Golovin
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 5.0.0.M5
>
>         Attachments: screenshot20111208101308.png
>
>
> 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/products/director_latest.zip
> 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 at dev.eclipse.org:/cvsroot/rt:org.eclipse.equinox/p2/bundles/org.eclipse.equinox.p2.installer

--
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