h1. Situation
ComponentA and productA build independently as different projects. During build process of productA, componentA will be checked for changes: if there are new changes in componentA, a new componentA version will be generated, and the new build result will be used to construct productA; otherwise, build result of latest version of componentA will be used instead.
h1. Demonstration
# To simulate new changes in componentA, _build condition_ of the [demo componentA configuration|http://demo.pmease.com/overview/55] is set to _always build_ so that a new componentA version will be generated whenever it is triggered.
# Visit [latest build of productA|http://demo.pmease.com/build/56.latest]. Hover mouse over the dependencies link in the build summary section, and you will see that current build of productA depends on most recent version of componentA.
# Click the run button to build productA. A new version will be generated in [componentA|http://demo.pmease.com/overview/55] besides the new version in [productA|http://demo.pmease.com/overview/56]. When new build of productA finishes, examine its dependency again, and it is now dependent on the newly generated version of componentA.
h1. Resolution
# Visit [repository setting of productA|http://demo.pmease.com/settings/56/repositories]. There are two repositories defined: _componentA_ and _productA_. Repository _productA_ is used to retrieve source code of productA from SCM, while repository _componentA_ is used to retrieve build result of componentA. Repository _componentA_ is defined to retrieve all published jars from componentA, with the build defined as _latest build (generate new if necessary)_.
# Visit [step setting of productA|http://demo.pmease.com/settings/56/steps]. Two checkout steps are defined to checkout repository _productA_ and _componentA_ respectively.
ComponentA and productA build independently as different projects. During build process of productA, componentA will be checked for changes: if there are new changes in componentA, a new componentA version will be generated, and the new build result will be used to construct productA; otherwise, build result of latest version of componentA will be used instead.
h1. Demonstration
# To simulate new changes in componentA, _build condition_ of the [demo componentA configuration|http://demo.pmease.com/overview/55] is set to _always build_ so that a new componentA version will be generated whenever it is triggered.
# Visit [latest build of productA|http://demo.pmease.com/build/56.latest]. Hover mouse over the dependencies link in the build summary section, and you will see that current build of productA depends on most recent version of componentA.
# Click the run button to build productA. A new version will be generated in [componentA|http://demo.pmease.com/overview/55] besides the new version in [productA|http://demo.pmease.com/overview/56]. When new build of productA finishes, examine its dependency again, and it is now dependent on the newly generated version of componentA.
h1. Resolution
# Visit [repository setting of productA|http://demo.pmease.com/settings/56/repositories]. There are two repositories defined: _componentA_ and _productA_. Repository _productA_ is used to retrieve source code of productA from SCM, while repository _componentA_ is used to retrieve build result of componentA. Repository _componentA_ is defined to retrieve all published jars from componentA, with the build defined as _latest build (generate new if necessary)_.
# Visit [step setting of productA|http://demo.pmease.com/settings/56/steps]. Two checkout steps are defined to checkout repository _productA_ and _componentA_ respectively.