[
https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBTIS-158:
----------------------------------
The "TP + aggregate" zip is now overwriting the Tycho-generated one since having
both artifacts seems unnecessary. Build and promote jobs should work even if we decide we
want to have both artifacts after all.
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