[
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