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

Rob Cernich (JIRA) jira-events at lists.jboss.org
Mon Aug 26 14:31:26 EDT 2013


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

Rob Cernich commented on JBTIS-158:
-----------------------------------

For JBTIS, we should have a single site, which includes all the IS features and makes reference to the JBT core site and the JBTIS TP (i.e. the JBTIS site is built with two associate sites).  This is easy peasy and works today.  The structure on jboss.org would be the same as what it has been, where the .../integration-stack URL is a composite site that contains references to each JBTIS version (e.g. ./aggregate/4.1.0, ./aggregate/4.1.1, ./aggregate/4.1.2, etc.).
                
> 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


More information about the jbosstools-issues mailing list