-
Bug
-
Resolution: Duplicate
-
Blocker
-
4.1.0.Beta1
-
None
Currently every component references nightly composite update site during the build to get dependencies. That leads to possibility to introduce cycle dependencies between components that is not detected by build.
Here is example of PR introduced a cycle between JST and VPE. Build works because JST have access to VPE BrowserSim through nightly composite update site.
The solution would be to reference specific nightly update sites for modules that are dependencies for current one.
In this case JST should have reference only to base composite nightly update site. That would solve cycle dependency detection problem and speed up the build because it would not require to download and analyse all metadata from jbosstools nightly composite update site.
- duplicates
-
JBIDE-16309 Move inter-JBT dependencies to component poms
- Closed
- is blocked by
-
JBIDE-15482 Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
- Closed
- is related to
-
JBIDE-13890 OpenOn for <div data-role="page">: "Open With BrowserSim" and "Open With Browser"
- Closed
- relates to
-
JBIDE-14610 Design http://download.jboss.org/jbosstools structure
- Closed
-
JBIDE-16309 Move inter-JBT dependencies to component poms
- Closed
-
JBIDE-16220 create an all-in-one build for JBT projects, using submodules
- Open