![]() libA => libZ: 1, libB => libZ: 1, no dependencyManagement on libZ.On Nuxeo code, we want that version being explicitly set in the dependencyManagement. If a project libA depends on the artifact libZ and another project libB also depends on libZ, then Maven will perform automatic version resolution to find the best match. Dependency convergence and consistencyĭependency version doubt is forbidden and transitive dependency upgrade is allowed but not the downgrade. Note that the SNAPSHOT dependency will be tolerated during nightly releases, but would make the LTS/FT release fail even with that exclusion. create a blocker JIRA issue requiring the dependency upgrade for next Nuxeo LTS/FT release. ![]() Profile/nightly/build/pluginManagement/plugins/maven-enforcer-plugin/configuration/rules/requireReleaseDeps/excludes org.nuxeo:nuxeo-ftest:*:zip If you need to temporarily use a SNAPSHOT plugin:Īdd it to the unCheckedPluginList in org.nuxeo:nuxeo-ecm You can also use variables named or : when releasing Nuxeo, the version replacement only applies on each POM on the parent version, the project version and all the properties named " nuxeo|marketplace.*version". LATEST and RELEASE keywords are forbidden, as well as pom.* properties but you can use variables prefixed " project." to reference any field of the POM that is a single value element. Using a property to avoid duplication is a good idea. The reporting plugins versions are not inherited from the pluginManagement, they must be repeated. Note that not only the version is managed, those definitions also include the exclusions, configuration. Define dependencies' versions in the dependencyManagement section and plugins' versions in the pluginManagement section.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |