|
|
There are 0 changes. View first change.
h1. Situation | ||
ComponentA and productA build independently as different project. ProductA uses build result of specified version of the componentA. The specified version will not change even if componentA has a new version. | ||
h1. Demonstration | ||
# Visit the demo project [productA|http://demo.pmease.com/build/62.latest/], it is configured to be dependent on version _1.0.10_ of [componentA|http://demo.pmease.com/build/61.latest/], and retrieves its build result _componentA-1.0.10.jar_ during its build process. Hover mouse over the dependencies link in the build summary section, and you will see that current build depends on version _1.0.10_ of componentA. | ||
# Switch to [componentA|http://demo.pmease.com/build/61.latest/], and click the run button to generate a new version of componentA. | ||
# Switch back to [productA|http://demo.pmease.com/build/62.latest/], and click the run button to build productA. When build finishes, examine its dependency again, and it is still using version _1.0.10_ of componentA. | ||
h1. Resolution | ||
# Visit [repositories definition of productA|http://demo.pmease.com/setting/repositories/62/]. There are two repositories defined: _component-a_ and _product-a_. Repository _product-a_ is used to retrieve source code of productA from SCM, while repository _component-a_ is used to retrieve build result of componentA. Repository _component-a_ is defined to retrieve all published artifacts from version _1.0.10_ of componentA. | ||
# Visit [step definitions of productA|http://demo.pmease.com/setting/steps/execution/62/]. Two checkout steps are defined to checkout repository _product-a_ and _component-a_ respectively. |