Bug 1259193
| Summary: | Missing dv-bom and teiid-odata artifacts. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Juraj Duráni <jdurani> |
| Component: | Distribution | Assignee: | Alex Szczuczko <aszczucz> |
| Status: | CLOSED NOTABUG | QA Contact: | Juraj Duráni <jdurani> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | aszczucz, atangrin, dlesage, jdurani, vhalbert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-09-09 15:49:41 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
Juraj Duráni
2015-09-02 07:30:08 UTC
Juraj, I'm not sure if dv-bom is an artifact that exists anywhere, at least I can't find it. I thought you might mean dv-dependency-management-all, which effectively is the DV BOM, but that's present. Could you please clarify why dv-bom is missing? Thanks. Alex, maven repository contains artifact org.jboss.dv.component.management:dv-component-management-aggregation:2.2.0.redhat-6. It is "pom" project and contains 2 modules: dv-parent, dv-bom. Artifact dv-parent is present, but dv-bom not. I thought that both of them should be present in repository. Juraj, Ok, I do see the <module>dv-bom</module> definition there. I think the confusion is because that module's artifactId doesn't follow convention, and is called something other than the module name. The pom located in the dv-bom/ subdirectory[1] has an artifactId of dv-dependency-management-aggregation (note: not the same as dv-component-management-aggregation), and is present in the repo. So dv-bom is just the module name, not the ID of any artifact. I wasn't aware that this was possible, so I'm just as surprised as you. [1] https://code.engineering.redhat.com/gerrit/gitweb?p=soa/soa-component-management.git;a=tree;f=src/main/resources/bom/dv-bom;h=c3fcdc9db629443dc9be71f106290d0ce7846e65;hb=refs/heads/jb-dv-6.2 [2] http://download.eng.bos.redhat.com/brewroot/repos/jb-dv-6.2-build/latest/maven/org/jboss/dv/component/management/dv-dependency-management-aggregation/ Alex,
I can confirm that dv-dependency-management-aggregation is present in the repo. Modules which are defined as modules of "dv-bom" do not follow convention either ("dv-dependency-management-supported" vs. "supported").
I think we can close the "dv-bom" part of this issue.
What about the second part ("teiid-odata")?
teiid-odata should be there, but doesn't seem to have been processed correctly by the repo generator. Still working on getting it included. Juraj, After investigating, the reason teiid-odata wasn't being included was that it is a war type artifact. Wars are specifically excluded from the repo, so it's expected that teiid-odata is missing. I've double checked with Van, and he confirms that the teiid-odata war isn't needed. Since both missing artifacts have resulted in no changes, I'll close this as NOTABUG. Is that ok with you? Since the hand-over deadline is imminent, I will close this bug now. It is ok with me. |