Bug 1220518
| Summary: | Optaplanner webexamples pom.xml unresolvable parent pom. | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Matyas Danter <mdanter> |
| Component: | OptaPlanner | Assignee: | Ryan Zhang <rzhang> |
| Status: | CLOSED EOL | QA Contact: | Jiri Locker <jlocker> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1.0 | CC: | gdesmet, kverlaen, lpetrovi, mbaluch, ncross, rzhang |
| Target Milestone: | ER5 | ||
| Target Release: | 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 20:01:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Matyas Danter
2015-05-11 18:07:18 UTC
This happens because the productized optaplanner-examples pom doesn't have a <repository> element for the customer enterprise maven repository. The community pom does have such an element, for the community maven repository. The result is that it doesn't work out the box and an meaningless error message appears during the build. Even if the user is smart enough to understand the missing repo problem and has time enough to mess with his settings.xml, they don't know the url of the missing maven repo. So the user reverts back to community code. Even our own SA's give up (due to lack of time) when facing this issue and use community code! Just make it work: add the enterprise maven repo and ignore the "don't add a repository element in a pom" guideline for examples poms. @Nick The examples are an exception to that wolf team rule, because the examples need to run out of the box. The solution is simple: productization should include the (canonical) customer enterprise maven repository in all examples poms, such as optaplanner-webexamples, optaplanner-examples, drools-examples, etc. The community code already does this and it works like a charm. Any other solution would involve educating our customers and Solution Architects to add a magical url in their ~/.m2/settings.xml and that is simply not practical, because most people just give up if it doesn't work out of the box - and move on to something that does "just work". I will add the redhat repository and remove the community repo into the quickstarts pom.xml. I think that should fix this. Just want to make sure, what exacly do you mean by "optaplanner product bits"? (In reply to jvahala from comment #8) > Just want to make sure, what exacly do you mean by "optaplanner product > bits"? I mean't the zip file titled BRMS-6.1.0/jboss-brms-6.1.0.GA-planner-engine.zip that is the downloadable product from the customer portal. @Ryan just addin ghte redhat repo in the brms quickstart does not suffice. We need it in the product poms of optaplanner-examples, optaplanner-webexamples, drools-examples and droolsjbpm-integration-examples too. The issue is not resolved. I've ran mvn clean install on webexamples pom.xml with renamed ~/.m2/settings.xml (as new user) and it can't be build. Non-resolvable parent POM for org.optaplanner:optaplanner:6.3.0.Final-redhat-3: Could not find artifact org.kie:kie-parent-with-dependencies:pom:6.3.0.Final-redhat-3 in Red Hat Product Repository (...) moving back to assigned Non-final bits are _not_ published into the public product repository (https://maven.repository.redhat.com/ga/). This will only work OOTB after we actually release the product. For now you will still need to use settings.xml with prod. repository. |