Hide Forgot
Created attachment 1137796 [details] Mixed client and server log Description of problem: If you do not specify settings.xml file and let Business Central use the default one from your .m2 directory, you may sometimes get really strange exception when you try to create a project using REST API. Version-Release number of selected component (if applicable): 6.3.0 ER1 Steps to Reproduce: 1. Start a fresh installation of Business Central. 2. Run ProjectTest from our test suite [1] 3. See the server log Actual results: IllegalStateException from HashMap Expected results: No exception or better exception is something is really wrong Additional info: I am not sure if this is the right way to use such settings.xml file. But in any case, the application should at least throw some exception that tells the user what exactly is not set up properly. [1] https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/blob/prod-6.3/test-kie-wb-rest/src/test/java/org/jboss/qa/brms/functional/ProjectTest.java#L34
Created attachment 1137799 [details] settings.xml in .m2 directory
Hi Thomas, could you please clarify if you don't use a custom location for settings.xml the error happens; but if you *do* use a custom location for settings.xml there is no error? For Unit Tests you can disable the feature that is checking the GAV being deployed is unique (https://issues.jboss.org/browse/BPMSPL-252) by setting the System Property "org.guvnor.project.gav.check.disabled" to "true". This of course does not resolve the issue you report, but may be useful for Unit Tests.
Hi Tomas, in addition to comment #2 could you please provide the POM for the Project you was trying to build via REST?
I think you have a repository defined in the Project's POM that is also in setting.xml...
@Tomas, it appears the issue is that settings.xml contains two Repository definitions with the same ID "jboss-public-repository-group" - one for dependency resolution and the other for plugins, with different URLs. Can you try changing the ID for one of them and re-try?
Verified on BRMS 6.3.0 ER2