Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-6780

Quarkus CLI sometimes doesn't show support scope when stream is set

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 3.27.0.CR1
    • devtools, team/eng
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Not use the stream setting.

      Show
      Not use the stream setting.
    • Hide
      • Prepare ~/.quarkus/config.yaml
      ---
registries:
- testingregistry:
    offering: redhat
    descriptor:
      artifact: "testingregistry:quarkus-registry-descriptor::json:1.0-SNAPSHOT"
    maven:
      repository:
        url: "https://registry-3-27-0-redhat-00002.apps.int.gpc.ocp-hub.prod.psi.redhat.com/maven"
- registry.quarkus.redhat.com
- registry.quarkus.io
      • Prepare Quarkus CLI
      jbang app install --name quarkus327 https://repo1.maven.org/maven2/io/quarkus/quarkus-cli/3.27.0/quarkus-cli-3.27.0-runner.jar
      • Prepare the maven repo
      wget http://download.eng.brq.redhat.com/rcm-guest/staging/quarkus/quarkus-platform-3.27.0.CR1/rh-quarkus-platform-3.27.0.CR1-maven-repository.zip

unzip -q rh-quarkus-platform-3.27.0.CR1-maven-repository.zip
cp rh-quarkus-platform-3.27.0.GA-maven-repository/maven-repository/* ~/.m2/repository/ -r
      • Prepare ~/.m2/settings.xml with this content:
      <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">

    <profiles>
        <profile>
            <id>red-hat-enterprise-maven-repository</id>
            <repositories>
                <repository>
                    <id>red-hat-enterprise-ga</id>
                    <name>redhat-ga</name>
                    <url>https://maven.repository.redhat.com/ga/</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>red-hat-enterprise-ga</id>
                    <url>https://maven.repository.redhat.com/ga/</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>
    <activeProfiles>
        <activeProfile>red-hat-enterprise-maven-repository</activeProfile>
    </activeProfiles>
</settings>
      • Execute quarkus327 ext list --support-scope --stream=3.27
      Show
      Prepare ~/.quarkus/config.yaml --- registries: - testingregistry: offering: redhat descriptor: artifact: "testingregistry:quarkus-registry-descriptor::json:1.0-SNAPSHOT" maven: repository: url: "https: //registry-3-27-0-redhat-00002.apps. int .gpc.ocp-hub.prod.psi.redhat.com/maven" - registry.quarkus.redhat.com - registry.quarkus.io Prepare Quarkus CLI jbang app install --name quarkus327 https: //repo1.maven.org/maven2/io/quarkus/quarkus-cli/3.27.0/quarkus-cli-3.27.0-runner.jar Prepare the maven repo wget http: //download.eng.brq.redhat.com/rcm-guest/staging/quarkus/quarkus-platform-3.27.0.CR1/rh-quarkus-platform-3.27.0.CR1-maven-repository.zip unzip -q rh-quarkus-platform-3.27.0.CR1-maven-repository.zip cp rh-quarkus-platform-3.27.0.GA-maven-repository/maven-repository/* ~/.m2/repository/ -r Prepare ~/.m2/settings.xml with this content: <settings xmlns= "http: //maven.apache.org/SETTINGS/1.2.0" xmlns:xsi= "http: //www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http: //maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd" > <profiles> <profile> <id>red-hat-enterprise-maven-repository</id> <repositories> <repository> <id>red-hat-enterprise-ga</id> <name>redhat-ga</name> <url>https: //maven.repository.redhat.com/ga/</url> <releases> <enabled> true </enabled> </releases> <snapshots> <enabled> false </enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>red-hat-enterprise-ga</id> <url>https: //maven.repository.redhat.com/ga/</url> <releases> <enabled> true </enabled> </releases> <snapshots> <enabled> false </enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>red-hat-enterprise-maven-repository</activeProfile> </activeProfiles> </settings> Execute quarkus327 ext list --support-scope --stream=3.27
    • ---

      In some environments when the offering is set in config.yaml, the Quarkus CLI with set --stream not show support scope. When the --stream is removed from Quarkus CLI command the support scope is show without problem.

      On QE environment, the RHEL have no problem, but windows show this bug. I have same problem on my machine, but my colleague don't have problem.

      The affected machines:
      quarkus ext list --support-scope --stream 3.27 not show any support scope e.g.

      ✬ quarkus-websockets WebSockets 3.27.0.redhat-00001 
✬ quarkus-websockets-client WebSockets Client 3.27.0.redhat-00001 
✬ quarkus-websockets-next WebSockets Next 3.27.0.redhat-00001

       
      The quarkus ext list --support-scope show

      ✬ quarkus-websockets WebSockets 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-client WebSockets Client 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-next WebSockets Next 3.27.0.redhat-00001 supported

      Using same commands on not affected machines the output is:

      ✬ quarkus-websockets WebSockets 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-client WebSockets Client 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-next WebSockets Next 3.27.0.redhat-00001 supported

      There can be some problem in my environment, but this should be at least documented. As we encounter this in multiple environments and customers can have same problem.

              olubyans@redhat.com Alexey Loubyansky
              jjedlick@redhat.com Jakub Jedlicka
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: