)]}'
{"README.md":[{"author":{"_account_id":18179,"name":"Kaiyan Sheng","email":"kaiyan.sheng@hpe.com","username":"kaiyan-sheng"},"change_message_id":"60d40503bfe8d846bd69a4c984a3dcfe51b5639f","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"# StackForge Build"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"There is a pom.xml in the base directory that should only be used for the StackForge build. The StackForge build is a rather strange build because of the limitations of the current StackForge java jobs and infrastructure. This build depends on jars that are built in the monasca-common build. That StrackForge build uploads the completed jars to http://tarballs.openstack.org/ci/monasca-common, but they are just regular jars, and not in a maven repository. Hence, the first thing the maven build from the base project does is execute the build in the download directory. That pom.xml executes the script download.sh which downloads the required jars from http://tarballs.openstack.org/ci/monasca-common and then uses maven to install them in the local directory. The maven install needs the pom.xml so that is pulled from the jar file and then changed to have the right version before the install."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"The monasca-common jars also need the base monasca-common pom.xml. So, that is pulled from gihtub.com and also installed in the local repository."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":1,"id":"fa69d971_03692f25","line":48,"range":{"start_line":48,"start_character":534,"end_line":48,"end_character":535},"updated":"2016-01-08 20:54:35.000000000","message":"Maybe it should be \"executing\"?","commit_id":"731029c0e1dbeaca7d74f120a45926b38f117197"},{"author":{"_account_id":11809,"name":"Craig Bryant","email":"craig.bryant@hpe.com","username":"craig-bryant"},"change_message_id":"cb09c7ccb02b4394d5666591d9eeb13afb4502a4","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"# StackForge Build"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"There is a pom.xml in the base directory that should only be used for the StackForge build. The StackForge build is a rather strange build because of the limitations of the current StackForge java jobs and infrastructure. This build depends on jars that are built in the monasca-common build. That StrackForge build uploads the completed jars to http://tarballs.openstack.org/ci/monasca-common, but they are just regular jars, and not in a maven repository. Hence, the first thing the maven build from the base project does is execute the build in the download directory. That pom.xml executes the script download.sh which downloads the required jars from http://tarballs.openstack.org/ci/monasca-common and then uses maven to install them in the local directory. The maven install needs the pom.xml so that is pulled from the jar file and then changed to have the right version before the install."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"The monasca-common jars also need the base monasca-common pom.xml. So, that is pulled from gihtub.com and also installed in the local repository."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-gfm","patch_set":1,"id":"fa69d971_664d9971","line":48,"range":{"start_line":48,"start_character":534,"end_line":48,"end_character":535},"in_reply_to":"fa69d971_03692f25","updated":"2016-01-08 21:01:18.000000000","message":"No, I\u0027m pretty sure execute is correct. It is going to execute that build, that build is not already executing","commit_id":"731029c0e1dbeaca7d74f120a45926b38f117197"}]}