]
Paul Leacu resolved JBTIS-162.
------------------------------
Resolution: Won't Fix
I understand the principle - I guess we'll stay with referencing the upstream TP
requirements - forming a JBTIS/ JBDSIS base/early access TP repo matrix.
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
Components: target-platform
Affects Versions: 4.1.3
Reporter: Nick Boldt
Assignee: Paul Leacu
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?