[
https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.s...
]
Paul Leacu commented on JBTIS-89:
---------------------------------
Hey Rob - some questions...
- Is this a JBDSIS-specific issue?
- Is it okay for the community tooling (JBTIS) to reference
download.jboss.org
repositories in its aggregated target platform?
- Is the correct solution for the production (JBDSIS) target platform to mirror all of
the existing non-core dependencies in one
https://devstudio.jboss.com/ repo?
- What about the JBT core dependencies? Should that also reference a devstudio repo?
Thanks!!
--paull
target platform repo should not contain repository references
-------------------------------------------------------------
Key: JBTIS-89
URL:
https://issues.jboss.org/browse/JBTIS-89
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Rob Cernich
Assignee: Paul Leacu
Priority: Critical
I don't see how this repo could be used in a jbds setting when it contains repository
references to jbt repositories. My understanding was that this repo only contained the
extra dependencies for jbt-is. By including these references, if this repo is used in
jbds, all those linked repos will be available too, polluting the pool of available
features/bundles.
--
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