h1. Situation
When a new snapshot version of a Maven library is generated, triggers all configurations using this snapshot library automatically.
h1. Demonstration
# In the demo set up, configuration [Product1|http://demo.pmease.com/overview/124] and [Product2|http://demo.pmease.com/overview/125] are maven configurations whose POM declared dependency to the library artifact which is built by configuration [Library|http://demo.pmease.com/overview/123].
# Run the [Library|http://demo.pmease.com/overview/123] configuration to generate a new snapshot of the library artifact.
# After the build finishes, new build of [Product1|http://demo.pmease.com/overview/124] and [Product2|http://demo.pmease.com/overview/125] will be fired automatically to do the verification.
h1. Resolution
# Check maven plugin setting in page _Administration/Plugin Management_, and make sure that the option _Resolve Effective POM_ has been enabled.
# Visit [general setting of the Library configuration|http://demo.pmease.com/settings/123/general], the _Trigger Dependents_ option is checked.
# Visit [step definition of the Library configuration|http://demo.pmease.com/settings/123/steps], the _maven build_ step simply calls Maven to build the library artifact. Maven goal does not matter here.
# Visit [step definition of the Product1 configuration|http://demo.pmease.com/settings/124/steps], the _maven build_ step simply calls Maven to build product1. POM file of product1 (brough to workspace by checkout step) contains dependency declaration to library artifact. Maven goal does not matter here.
# Visit [step definition of the Product2 configuration|http://demo.pmease.com/settings/125/steps], the _maven build_ step simply calls Maven to build product2. POM file of product2 (brough to workspace by checkout step) contains dependency declaration to library artifact. Maven goal does not matter here.
When a new snapshot version of a Maven library is generated, triggers all configurations using this snapshot library automatically.
h1. Demonstration
# In the demo set up, configuration [Product1|http://demo.pmease.com/overview/124] and [Product2|http://demo.pmease.com/overview/125] are maven configurations whose POM declared dependency to the library artifact which is built by configuration [Library|http://demo.pmease.com/overview/123].
# Run the [Library|http://demo.pmease.com/overview/123] configuration to generate a new snapshot of the library artifact.
# After the build finishes, new build of [Product1|http://demo.pmease.com/overview/124] and [Product2|http://demo.pmease.com/overview/125] will be fired automatically to do the verification.
h1. Resolution
# Check maven plugin setting in page _Administration/Plugin Management_, and make sure that the option _Resolve Effective POM_ has been enabled.
# Visit [general setting of the Library configuration|http://demo.pmease.com/settings/123/general], the _Trigger Dependents_ option is checked.
# Visit [step definition of the Library configuration|http://demo.pmease.com/settings/123/steps], the _maven build_ step simply calls Maven to build the library artifact. Maven goal does not matter here.
# Visit [step definition of the Product1 configuration|http://demo.pmease.com/settings/124/steps], the _maven build_ step simply calls Maven to build product1. POM file of product1 (brough to workspace by checkout step) contains dependency declaration to library artifact. Maven goal does not matter here.
# Visit [step definition of the Product2 configuration|http://demo.pmease.com/settings/125/steps], the _maven build_ step simply calls Maven to build product2. POM file of product2 (brough to workspace by checkout step) contains dependency declaration to library artifact. Maven goal does not matter here.