[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=12799524#comment-12799524 ] 

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

{quote}
If the associate site references to JBT core are the actual matching stable urls and not version specific urls then I don't see much problem.
{quote}

Yes, they are: 

https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jbosstools/site/pom.xml#L237-238

FWIW, the same is true for JBT itself, as JBT refers to a specific TP site and therefore it too cannot be tested in isolation (eg., installation against a different TP):

https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L33

So... we're good (or as good as possible w/o extra install-time complication). 

[~maxandersen] Is a zip of JBTIS + JBTIS TP still required, given the new "Thou Shalt Only Use Central" directive?
                
> 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