[
https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen edited comment on JBIDE-14448 at 5/15/13 3:23 AM:
----------------------------------------------------------------------
Suggestion (don't implement without testing in seperate branch!):
A) Remove nightly composite site from parent pom/TPC.
B) List the dependent composite site individually in root pom of components.
Question - how do we maintain this between branches/main platform.
Should have a naming scheme so we do not need to change this in every dev cycle for every
component.
was (Author: maxandersen):
Suggestion (don't implement without testing in seperate branch!):
A) Remove nightly composite site from parent pom/TPC.
B) List the dependent composite site individually in root pom of components.
Build doesn't detect cycle dependencies between JBossTools
modules
------------------------------------------------------------------
Key: JBIDE-14448
URL:
https://issues.jboss.org/browse/JBIDE-14448
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Beta1
Reporter: Denis Golovin
Assignee: Nick Boldt
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.
--
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