[jbosstools-issues] [JBoss JIRA] (JBIDE-14448) Build doesn't detect cycle dependencies between JBossTools modules

[Denis Golovin (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776510#comment-12776510 ] 

Denis Golovin commented on JBIDE-14448:
---------------------------------------

It is time to cleanup download.jboss.org and develop structure that would easy to understand and navigate, what we have now looks like .... lets say politely - confusing. 

We have several types of objects which names should be presented in URL:
# Project Name: jbosstools
# Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
# Subproject Name: core, soatools
# Distribution Type: updates|builds
# Bits Type: stable|development|nightly
# Targeted Eclipse: indigo|juno|kepler
# You name it ...

Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
# aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
# jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
# jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits


                
> 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