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

[Rob Cernich (JIRA)]

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

Rob Cernich edited comment on JBTIS-158 at 8/29/13 12:57 PM:
-------------------------------------------------------------

The linked PR creates an additional zip in the site project.  The structure of the zip is as follows:

{noformat}
./aggregate/${project.version}/<jbds-is-repo>
./targetplatform/${project.version}/<jbds-is-tp-repo>
{noformat}

The root composite site includes children for ./aggregate and ./targetplatform.  There are no repository references in the jbds-is-repo.  The jbds-is-tp-repo is created by mirroring the jbtis tp from a url specified in the pom configuration.

The one drawback is that you cannot install directly using the zip; you need to expand it first (the relative paths don't seem to work).

When deploying to server, you should be good to simply expand the zip in the desired location for the initial site.  For updates, you will have to expand all but the composite*.xml files and will have to add the new version(s) to the existing composite*.xml files on the server.

Let me know what you think of this.
                
      was (Author: rcernich):
    The linked PR creates an additional zip in the site project.  The structure of the zip is as follows:

./aggregate/${project.version}/<jbds-is-repo>
./targetplatform/${project.version}/<jbds-is-tp-repo>

The root composite site includes children for ./aggregate and ./targetplatform.  There are no repository references in the jbds-is-repo.  The jbds-is-tp-repo is created by mirroring the jbtis tp from a url specified in the pom configuration.

The one drawback is that you cannot install directly using the zip; you need to expand it first (the relative paths don't seem to work).

When deploying to server, you should be good to simply expand the zip in the desired location for the initial site.  For updates, you will have to expand all but the composite*.xml files and will have to add the new version(s) to the existing composite*.xml files on the server.

Let me know what you think of this.
                  
> 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