Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.2 M2
-
Component/s: Build, Infrastructure and Tests
-
Labels:None
-
Similar issues:
XCOMMONS-29Provide xwiki.clirr.previous.version property in the root pom XCOMMONS-106Upgrade Maven Site plugin to version 3.0 XCOMMONS-334Validate versions for POM dependencies XCOMMONS-175Maven resolution sometimes fails to properly determinate dependency version XCOMMONS-94Set the minimum required Maven version (3.0) to build XWiki in the POM XCOMMONS-102 Upgrade Maven Bundle plugin to version 2.3.6 XCOMMONS-128Upgrade to Maven Clover plugin 3.1.4 and fix the Clover build XCOMMONS-386Commons fails to build due to a RESTlet dependency not present on Maven Central XCOMMONS-138Add new XWiki Commons Text module for text-related generic APIs XCOMMONS-296Use Jacoco for the Quality Profile
Description
That's because commons plugins are defined with $
{project.version}which is current version and not commons version. That makes maven trying to find commons plugins with the current project version as version which is not going to work most of the time.
Issue Links
- blocks
-
XWIKI-6901
Fail to build a project which has platform pom as parent and has different version
-
- relates to
-
XRENDERING-130
Provide rendering.version property
-