-
Sub-task
-
Resolution: Done
-
Blocker
-
4.1.0.Alpha1
-
None
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:
[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]
- is duplicated by
-
JBIDE-13316 Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)
- Closed
- is related to
-
JBIDE-13232 refactor target platforms' GAVs, names, labels (was target platforms has the same name)
- Closed
- relates to
-
JBIDE-13629 Update Juno SR2 and Kepler M5a target platforms to include EGit 2.3.1
- Closed