Bug 1220518 - Optaplanner webexamples pom.xml unresolvable parent pom.
Summary: Optaplanner webexamples pom.xml unresolvable parent pom.
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: OptaPlanner
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER5
: 6.2.0
Assignee: Ryan Zhang
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-11 18:07 UTC by Matyas Danter
Modified: 2020-03-27 20:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:01:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1220553 0 high CLOSED Need to fix the examples pom.xml to include product maven repo. 2021-02-22 00:41:40 UTC

Internal Links: 1220553

Description Matyas Danter 2015-05-11 18:07:18 UTC
Description of problem:


Version-Release number of selected component (if applicable):
BxMS 6.1 Business Resource Planner

How reproducible:
every time

Steps to Reproduce:
1. unzip the optaplanner product bits
2. import the maven project from [unzipped dir]/webawxamples/sources into eclipse
3. pom.xml references parent pom that doesn't exist.

Actual results:
maven project cannot be built without modification

Expected results:
maven project ha s the correct references

Additional info:

Comment 2 Geoffrey De Smet 2015-05-13 12:26:24 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.

Comment 5 Geoffrey De Smet 2015-09-09 08:18:52 UTC
@Nick The examples are an exception to that wolf team rule, because the examples need to run out of the box.

Comment 6 Geoffrey De Smet 2015-09-09 08:26:56 UTC
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".

Comment 7 Ryan Zhang 2015-09-09 09:54:23 UTC
I will add the redhat repository  and remove the community repo into the quickstarts pom.xml.
I think that should fix this.

Comment 8 jvahala 2015-11-04 12:13:41 UTC
Just want to make sure, what exacly do you mean by "optaplanner product bits"?

Comment 9 Matyas Danter 2015-11-04 12:22:53 UTC
(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.

Comment 10 Geoffrey De Smet 2015-11-04 12:54:04 UTC
@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.

Comment 11 jvahala 2015-11-04 13:02:15 UTC
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

Comment 12 Petr Široký 2015-11-04 13:45:06 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.