> I've patched my pom to use the exact version 1.2 but it still fail to > resolve to hamcrest12 in rawhide. Because by patching your POM you fixed only one problem. The second one remains open. > In fact hamcrest12(upstream > version 1.2) is newer than hamcrest (upstream version 1.1). > Shouldn't this make hamcrest obsolete? I agree that in generall case the newest version should be default system version. But it's really up to maintainers to decide which version of the library will be default one and which one will be compatibility package. In case of hamcrest it looks like they decided that 1.2 will be compatibility package. > I also updated my local dependency map to use 1.2 but maven still > resolves to use hamcrest. Please help thanks. It's because of the bug in hamcrest12 (#917857) > ========== how I patched it ======== > %pom_remove_dep org.hamcrest:hamcrest-core > %pom_remove_dep org.hamcrest:hamcrest-library > %pom_xpath_inject "pom:dependencies" > "<dependency><groupId>org.hamcrest</groupId><artifactId>hamcrest-core</artifactId><version>1.2</version><scope>test</scope></dependency>" > %pom_xpath_inject "pom:dependencies" > "<dependency><groupId>org.hamcrest</groupId><artifactId>hamcrest-library</artifactId><version>1.2</version><scope>test</scope></dependency>" This should work. -- Mikolaj Izdebski -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
