[
https://jira.jboss.org/jira/browse/JBIDE-4200?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-4200:
-----------------------------------
We will never have two builds of different types w/ the same timestamp.
And when we switch to use different tags in the maps, so that individual plugins/features
only change when their contents change (rather than with every build, as we do it now),
then it won't matter if a jar is built via an R or N build, because the bits will be
identical, right down to the generated feature suffix hash/digest.
We can also make the naming a little smarter:
3.1.0.v200911091234-M1-H5-N
3.1.0.v200911101234-M1-H9-R
...
3.1.0.v200911091234-RC1-H20-N
3.1.0.v200911101234-RC1-H25-R
...
3.1.0.v200912091234-R-H30
I suppose really the type suffix is meaningless at this point since an N build == an R
build except for that letter. We could drop the buildType suffix entirely.
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