[
https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin....
]
Rob Cernich commented on JBTIS-158:
-----------------------------------
Actually, a better structure might be:
compositeContent.xml (one child, ./<version>)
compositeArtifacts.xml (one child, ./<version>)
<version>/compositeContent.xml
<version>/compositeArtifacts.xml
<version>/<version>-jbds-is
targetplatform/compositeContent.xml (one child, ./<version>-jbds-is-tp)
targetplatform/compositeArtifacts.xml (one child, ./<version>-jbds-is-tp)
targetplatform/<version>-jbds-is-tp
That way you still have a self contained zip, but, if you want, when you deploy, you can
separate things out.
That would work nicely with a site structure like:
7.0/integration-stack/<versions> (where ./<version> would go)
7.0/integration-stack/targetplatform/<versions> (where
./targetplatform/<version> would go
Anyway, you pick the root structure you want, but I think this bridges the gap.
Obviously, you wouldn't move across the composite*.xml files in ./ or
./targetplatform.
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