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

[ https://issues.jboss.org/browse/JBIDE-14448?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14448: ------------------------------------ OK, so what I'm hearing here is that we need two things for each and every project: * a way to easily build a given project based on SPECIFIC upstream builds of dependencies (eg., Base build #456 and Server build #567), both locally and in Jenkins * a way to easily build a given project based on THE LATEST upstream builds of dependencies for a given stream (_40, _410, _41, _master) Therefore we need to: * replace staging/JOB_NAME/all/repo/ with ci/JOB_NAME/BUILD_ID/all/repo/ when publishing [0] (JBIDE-15482) * automatically clean out old builds [1] to avoid filling download.jboss.org and crashing it (JBIDE-15482) * a tool [2] to generate a composite site on dl.jb.org, fed a series of URLs for upstream projects against which you want to build (using the latest by default + some static sites) [3] * a tool [2] to generate a composite site *locally*, fed a series of URLs for upstream projects SPECIFIC BUILDS against which you want to build (likely a subset of the full site above [3] [0] https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/cleanu... [2] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/genera... [3] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... Once all the above is in place, we would then need a profile or -Dflag in parent pom (such as * -Djbosstools-nightly*) to allow a user to point at their locally-generated composite site (from the previous item) instead of using the default composite. For example, we might want to do this: {code} wget https://raw.github.com/jbosstools/jbosstools-build-ci/master/util/generat... && chmod +x generateCompositeStagingSiteMetadata.sh ./generateCompositeStagingSiteMetadata.sh -NAME 'My Local Upstream Composite Site' -DESTINATION /tmp/my-local-site/ -SITES http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... {code} then this: {code} cd ~/path/to/jbosstools-livereload mvn clean verify -Djbosstools-nightly=file:///tmp/my-local-site/ {code} ... and boom goes the dynamite. -- 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