-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
The QS in EAP XP 1.0.0.GA-CR1 contain instructions that create project from scratch using mvn archetype. Such projects do not have repositories defined that are needed for QS and are defined in QS parent pom:
<repositories>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>${maven.repository.url}</url>
<layout>default</layout>
</repository>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
<id>jboss-enterprise-maven-repository</id>
<name>JBoss Enterprise Maven Repository</name>
<url>${maven.redhat.repository.url}</url>
<layout>default</layout>
</repository>
</repositories>
Without the repos defined, the BOMs and other dependencies that are not present in maven central won't be found.
Affected QS:
- microprofile-config
- microprofile-fault-tolerance
- microprofile-health
- microprofile-jwt
- microprofile-metrics
- microprofile-openapi
- microprofile-opentracing
- microprofile-rest-client
- clones
-
-
- Verified
-
