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

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

The reason I recommend the zip is because it is an artifact that is easy to move around, whether you want to use it specifically for offline installation or not.  If you'd rather leave this as a directory, that's fine too.  To compare it to a normal site project, it's the same as the site in your project's target directory or the site zip in the target directory, use whichever is better for you.

One other thing, given that these will roll up under something like 7.0/integration-stack/ where there may be many (e.g. 7.1.0, 7.1.1, etc.), it probably makes sense to remove the 7.1.0 directory from the hierarchy, as that is probably where this site would live, otherwise, you'll be modifying the composite files on the servers.  So, the server might look something like: (at <integration-stack-root>

./compositeContent.xml (child entries for 7.1.0, 7.1.1, etc.)
./compositeArtifacts.xml (child entries for 7.1.0, 7.1.1, etc.)
./7.1.0 (composite site listed above; i.e. unzip it into the 7.1.0 directory)

Just my two cents.  If you'd like, I can modify the project.  We need to get something done.

Paul, when you test this site, do you see things like Graphiti?  or just the IS bits?
                
> 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