[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4200:
--------------------------------------------
hmm - I can't download the patch ... could you reattach it ?
What is phase set to for releases ?
With respect to this change does eclipse got a writeup why it is better to have the date
being the siginificant qualifier ?
My problem with this is that a nightly build:
3.1.0.v200911091234-M1-H5-N
would be considered "updatable" from this release build:
3.1.0.v200910091234-R1-H5-R
Where as in the "old" system we had the release qualifer earlier in the name
meaning no nightly builds of 3.1.0 could ever overwrite a Release build (which imo is how
it should be since any nightly build with a newer date but same "old" version is
a bad thing)
Change qualifiers on zips and jars to support Milestones and RCs
instead of Alphas, Betas, CRs, GA
--------------------------------------------------------------------------------------------------
Key: JBIDE-4200
URL: https://jira.jboss.org/jira/browse/JBIDE-4200
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.M1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
Attachments: devstudio-trunk.patch, mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Jars and zips currently look like 3.1.0.Alpha1-yyyymmddHHMM-H###
To support a more Eclipse-like naming convention involving milestones, we need to switch
to:
3.1.0.vyyyymmddHHMM-PP-H###-T
Where PP = phase, eg., M1, H### = Hudson build number, and T = type, eg., N, I, S, or R.
(Only N and R are currently supported.)
This will guarantee that regardless of where a build is produced (ie., in whatever phase)
it can always be installed onto an older version because the qualifier will always
increase w/ time, regardless of additional suffixes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira