[jbosstools-issues] [JBoss JIRA] (JBTIS-357) Create a new JBDSIS-based independent installer bundle

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBTIS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBTIS-357:
-----------------------------
    Description: 
a: Check for the existance of an inserted zip
b: if found, present user with the option to install one or more of the 3 feature groupings (based on product definitions). These are the same groupings seen in Central.

So the logic for this "if found do..." should be built into the installer by default (and ignored for Core); should IS need to respin the logic after we GA, they'll need to rebuild from our repo. Not ideal but better than having to fork the installer entirely.
 

  was:
a: Check for the existance of an inserted zip
b: if found, present user with the option to install one or more of the 3 feature groupings (based on product definitions). These are the same groupings seen in Central.



> Create a new JBDSIS-based independent installer bundle
> ------------------------------------------------------
>
>                 Key: JBTIS-357
>                 URL: https://issues.jboss.org/browse/JBTIS-357
>             Project: JBoss Tools Integration Stack
>          Issue Type: Feature Request
>          Components: distribution
>            Reporter: Paul Leacu
>            Assignee: Nick Boldt
>
> a: Check for the existance of an inserted zip
> b: if found, present user with the option to install one or more of the 3 feature groupings (based on product definitions). These are the same groupings seen in Central.
> So the logic for this "if found do..." should be built into the installer by default (and ignored for Core); should IS need to respin the logic after we GA, they'll need to rebuild from our repo. Not ideal but better than having to fork the installer entirely.
>  



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)