|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Confirmed with a repository added from a profile and containing an updated parent POM, providing a new dependency in its dependencyManagement.
The POM parsing fails with "'dependencies.dependency.version' for org.quartz-scheduler:quartz-oracle:jar is missing".
This error corresponds to not using the profile configured in the job ("qa" in my case):
$ mvn help:effective-pom -Pqa |grep -C2 quartz-oracle <dependency> <groupId>org.quartz-scheduler</groupId> <artifactId>quartz-oracle</artifactId> <version>1.8.6</version> </dependency>$ mvn help:effective-pom |grep -C2 quartz-oracle Validation Messages: [0] 'dependencies.dependency.version' is missing for org.quartz-scheduler:quartz-oracle:jarThe suggested workaround, I saw in some mailing list thread, to provide a custom settings which activates the wanted profile doesn't work neither.