[jbosstools-issues] [JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Tue Aug 27 11:03:27 EDT 2013
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799626#comment-12799626 ]
Nick Boldt commented on JBTIS-158:
----------------------------------
Yes, but the TP is built *BEFORE* the rest of the aggregates, by necessity, as it's a prereq for the child projects themselves. So you can't very well build the TP and the aggregate in the same reactor, in order to produce some larger TP + aggregate zip.
I suppose you could fetch the latest TP site as a zip during the build (if in fact JBTIS' TP was being published that way, like we do for JBT), unpack it, create a zip containing that + the JBTIS aggregate site, and publish that uberzip.
In the interested of parallel dir trees, would this be better?
integration-stack/aggregate/<versions> (where ./<version> would go)
integration-stack/targetplatform/<versions> (where ./targetplatform/<version> would go)
> 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