Hide Forgot
Description of problem: In uberfire component, the properties defined as: ... <javax.inject.version>1</javax.inject.version> <cdi-api.version>1.0-SP4</cdi-api.version> <weld-spi.version>1.1.Final</weld-spi.version> <weld.version>1.1.13.Final</weld.version> ... But in community bom , ipbom and jboss eap bom, the properties are defined as: ... <version.org.jboss.weld.weld>1.1.13.Final-redhat-1</version.org.jboss.weld.weld> <version.org.jboss.weld.weld-api>1.1.Final-redhat-2</version.org.jboss.weld.weld-api> ... Please use the same version format and the same properties values for the same artifact in uberfire. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Please notice that there are several artifacts versions defined in uberfire are different from the ones defined in community bom. For example: lucene mockito-all helix .... Please also make sure the common artifact use the same version besides the version format.
Kindly remind that mvel version:2.1.Beta8 is also different.
A side build problem: uberfire contains lucene-core in the dependency tree (am I correct?) Should we also explicitly define it in dependencyManagment section?
Fix pushed to master and product branch of uberfire repository. As commit message says, still room for improvement on pom's - but for now i think it's fine. (master) https://github.com/droolsjbpm/uberfire/commit/405bae6eb (0.3.x) https://github.com/droolsjbpm/uberfire/commit/72fde1ea0
VERIFIED by checking the commits.