Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-13386 Create dedicated Git repo for target platforms
  3. JBIDE-13408

investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Blocker
    • 4.1.0.Alpha2
    • 4.1.0.Alpha1
    • target-platform
    • None

    Description

      investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have final versions rather than ongoing snapshots.

      Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error:

      https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1
      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/target-platforms/jbdevstudio/multiple/4.21.3.Final/multiple-4.21.3.Final.pom. Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1]

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users JBIDE-13316 Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13232 refactor target platforms' GAVs, names, labels (was target platforms has the same name)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-13629 Update Juno SR2 and Kepler M5a target platforms to include EGit 2.3.1

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              mistria@redhat.com Mickael Istria
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: