| Summary: | Missing dependency in maven repository - quickstarts cannot be built | ||
|---|---|---|---|
| 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.3.0 | CC: | aszczucz, jolee, mbaluch, thauser, 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: | 2016-03-17 12:01:07 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: | |
|
Description
Juraj Duráni
2016-03-16 09:48:51 UTC
The maven error makes it seem like it's related to the integration-platform-parent pom, but if you look closely, the root exception is a JVM-internal error: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty Searching this indicates that the trust store path is probably misconfigured, and since maven is trying to download via HTTPS, it makes sense that would be required. So, this doesn't look a build problem. Please check the trust store in your local JVM is configured correctly? Thanks. The exception is only result not the cause. The maven failed to find artifact in zip repository, therefore it tries to find it in central and fails because of bad configuration. But the point still is, that it should not even try to look for the artifact in maven central, because the artifact should be in the zip repository. > Artifact jboss-integration-platform-parent: <parent> <groupId>org.jboss</groupId> <artifactId>jboss-parent</artifactId> <version>16</version> <relativePath></relativePath> </parent> <groupId>org.jboss.integration-platform</groupId> <artifactId>jboss-integration-platform-parent</artifactId> > Versions in the zip repository: 10-redhat-2 11-redhat-1 14.0.0.redhat-1 16.0.0.redhat-1 8-redhat-1 9-redhat-1 Sorry, I confirm jboss-parent:16 isn't present, and is set as the parent of jboss-integration-platform-parent:6.0.0.CR30-redhat-1. I'm not currently sure why the maven repository generator missed it. I asked pkocandr, and he reminded me that any artifacts that are present in Maven Central are deliberately filtered from the repo zips. A missing jboss-parent:16 is compliant with the MRRC requirements[1] since it is present in Central[2], and the requirements state all artifacts must "be included in the product maven repository or be available in Maven central" So, I think my original suggestion (fix the JVM trust store) stands, as the quickstarts are allowed to require access to Maven Central. Juraj, if you agree I will close this as NOTABUG. [1] https://mojo.redhat.com/docs/DOC-187749 [2] http://central.maven.org/maven2/org/jboss/jboss-parent/16/ OK, close the bug. Anyway, there is still at least one missing dependency. I logged a new issue - https://bugzilla.redhat.com/show_bug.cgi?id=1318684 |