[JBoss JIRA] (JBTIS-162) Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-162?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-162:
-----------------------------
Description:
JBT has two types of .target files:
* multiple [1], which references multiple upstream URLs from which its IUs are sourced, and
* unified [2], which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL.
[1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
[2] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
Should JBTIS have a similar notion?
was:
JBT has two types of .target files:
* multiple, which references multiple upstream URLs from which its IUs are sourced, and
* unified, which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL.
Should JBTIS have a similar notion?
> Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?
> --------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-162
> URL: https://issues.jboss.org/browse/JBTIS-162
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.3
> Reporter: Nick Boldt
>
> JBT has two types of .target files:
> * multiple [1], which references multiple upstream URLs from which its IUs are sourced, and
> * unified [2], which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL.
> [1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> [2] https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> Should JBTIS have a similar notion?
--
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
10 years, 10 months
[JBoss JIRA] (JBTIS-162) Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?
by Nick Boldt (JIRA)
Nick Boldt created JBTIS-162:
--------------------------------
Summary: Should JBTIS have a "unified" target platform which references a single URL instead of a myriad of them?
Key: JBTIS-162
URL: https://issues.jboss.org/browse/JBTIS-162
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: target-platform
Affects Versions: 4.1.3
Reporter: Nick Boldt
JBT has two types of .target files:
* multiple, which references multiple upstream URLs from which its IUs are sourced, and
* unified, which references a single update site, which is the published site generated from materializing the multiple target, then replacing all the URLs w/ that new single, unified URL.
Should JBTIS have a similar notion?
--
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
10 years, 10 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-158:
----------------------------------
FWIW - I built from master:
cd target-platform; mvn -U -Dtycho.localArtifacts=ignore clean install
cd ../devstudio
mvn -U -Dtycho.localArtifacts=ignore -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ clean install # since we don't have a 7.0.0 agg yet
it built but wouldn't install - will look at it (Missing requirement: JBoss Runtime jBPM Detector 4.5.200.Final-v20130815-1941-B2008 (org.jboss.tools.runtime.jbpm.detector.feature.feature.group 4.5.200.Final-v20130815-1941-B2008) requires 'org.jboss.tools.runtime.core 0.0.0' but it could not be found)
> 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
10 years, 10 months