whats missing here ? seems to me it renders it correctly ?
i.e.
3.4.0.M1-v20120821-2129-H1039
/max
On 22 Aug 2012, at 18:24, Nick Boldt <nboldt(a)redhat.com> wrote:
FWIW, this is an incomplete implementation. The features' &
plugins' qualifiers have been reordered as noted below via the parent pom config, but
the update site index pages (site names as generated via the XSL) have as yet not been:
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk....
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk....
etc.
I've assigned myself this JIRA to finish the cleanup work:
https://issues.jboss.org/browse/JBDS-2251
On 08/22/2012 08:07 AM, Max Rydahl Andersen wrote:
>>>>
>>> I did not say *remove* the date, I said it should not be the significant
decider for p2.
>>>
>>> i.e. Release of a version should make any nightly/snapshot builds of that
version invalid; today it does not because the data comes *before* the release type flag.
>>>
>>> proper versioning that has semantic API meaning instead of just rely on what
date the build was made.
>>
>> In trunk it is now uses release type in front of the date. It was fixed a month
ago and works fine since.
>> I uses '${BUILD_ALIAS}-v'yyyyMMdd-HHmm' for local builds and
'${BUILD_ALIAS}-v'yyyyMMdd-HHmm'-H${BUILD_NUMBER}' for hudson
>
> Oh - nice; that is news to me! Didn't see any notification on this ?
Shouldn't we get that out since this changes things for QE/testers/bleeding edge
installs
> and bumping versions becomes that more important.
>
> /max
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com