[jbosstools-issues] [JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

[Paul Leacu (JIRA)]

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

Paul Leacu commented on JBTIS-654:
----------------------------------

Hey [~dgolovin] [[~akazakov] - I know you guys are extremely busy with the summit release.  This is a post-summit enhancement request.

I talked with [~maxandersen] about how best to architect this support.  He was of the opinion that it would make
more sense to parameterize the devstudio installer support to allow it to take a platform-specific runtime as
opposed to migrating the p2-director and izpack installer infrastructure over in the integration stack build.

Having migrated the two over in a prototype it did amount to a near duplication of the code.  I'm currently successfully using Denis' p2 director installer enhancement (AdditionalFeaturesSpec.json) to allow the IS to specify its features into the devstudio installer.  We'll release that in the Mars stream.  What I'd like is to extend that...

Is it possible to get into a future devstudio 10.0.x (neon) release enhanced installer support where a user could specify:

1.  A stand-alone installer jar - this would be the devstudio-is (Integration Stack) stand-alone installer.
2.  A compressed runtime (zip) that would be expanded into an appropriate runtime folder within the devstudio footprint (using the EAP one or a seperate folder).  This would likely go into its own pack ID - "Red Hat JBoss Developer Studio Component Runtime" - something like that?
ref: jboss-fuse-full-6.3.0.redhat-075.zip
3.  A specific IzPack panel binary - tailored to the platform we're offering.  This would be installed into the specified IS installer (1) to create the new extended installer based on what was passed in.,

The goal would be to provide an abstract way to specify a runtime zip and installer panel associated with the runtime into a pre-existing stand-alone installer.  The existing runtime detection would need to be augmented as well.  That would allow greater flexibilty in creating full stand-alone installers for Fuse, Teiid Designer, etc and leverage the existing devstudio installer to the greatest extent.

I'm open to any other ideas as well.

WDYT?

> JBDSIS stand-alone installer
> ----------------------------
>
>                 Key: JBTIS-654
>                 URL: https://issues.jboss.org/browse/JBTIS-654
>             Project: JBoss Tools Integration Stack
>          Issue Type: Feature Request
>          Components: distribution
>    Affects Versions: 9.0.0.GA
>            Reporter: Paul Leacu
>            Assignee: Paul Leacu
>             Fix For: 9.0.1.GA
>
>         Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling.  This Jira is specifically related to the JBDSIS installer.  Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8.  (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar.  i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.0.Beta1/jboss-devstudio-is-installer-9.0.0.Beta1-proto.jar
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/devstudio/installer



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)