[
https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-14448:
----------------------------------------
Each component should have in its pom a "targetJBTVersion" which will then used
to resolve URLs defined in parent pom
"http://download.jboss.org/jbosstools/updates/development/${targetJBTVersion}/_composite_"
and stuff like that.
Either all components change it, or we need to change it in parent pom and then ask
component to update to newer parent. Anyway, they need to change something. However, this
property could be provided by job configs, just like the current version of TP nowadays.
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