[
https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13316 at 2/1/13 12:38 PM:
-------------------------------------------------------------
+1, this looks like a solution to this jira and to JBIDE-13408, too:
a) push to staging automatically by CI build
b) then get someone w/ access to push from staging to production (manually).
Ref:
https://community.jboss.org/wiki/MavenDeployingARelease
was (Author: nickboldt):
+1, this looks like a solution to JBIDE-13408.
Improve versioning for TP using standard Maven way (no SNAPSHOT for
stable and tags)
------------------------------------------------------------------------------------
Key: JBIDE-13316
URL:
https://issues.jboss.org/browse/JBIDE-13316
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.1.0.Alpha1
Currently, we deal with explicit versions in folder names that make it confusing to
understand how target-platforms are versioned.
Instead, we should use usual Maven way and Git branches: one Git branch for each version
of TPs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira