[jbosstools-issues] [JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBTIS-158:
----------------------------------

Hard coding a reference to your specific TP is a bad idea.

Hard coding a reference to a URL which won't ever change, but which is a composite site pointing at your latest compatible TP is a good idea.

Why, you ask?

Using this extra layer of obfuscation / indirection allows us to - if we should need to - release an updated Kepler-based target platform for a future JBTIS 4.1.x release, and backport that into the previous 4.1.2 release so that all existing previously installed users can benefit from the update.

(In the past, this has been critical to roll out performance and UI bugs in Eclipse or WTP to existing JBT users. We've had Juno performance issues and SWT bugs/patches in Eclipse 3.6 and 3.7, too.) Being able to push an updated TP out to existing installed users is vital.
                
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
>                 Key: JBTIS-158
>                 URL: https://issues.jboss.org/browse/JBTIS-158
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: distribution
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site.  The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS 
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS 
> JBT IS TP
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira