[jbosstools-dev] Migration to jgit timestamps

[Nick Boldt]

(Previously, on "migrating to jgit timestamps"...)

Instead of a BUILD_ALIAS like Alpha1 or Beta1, which forces users to
download a whole JBT or devstudio install each time we release a new
milestone, plugins and features will soon use the timestamp of their
last change in github.

Note that two plugins will continue to have a BUILD_ALIAS applied:
foundation.core & devstudio.core.central, which define the version of JBoss
Tools / devstudio used by ide-config.properties to assign the correct
URLs for Central and quickstarts. But as you may have seen in another
thread, we are now using milestone numbers instead of quality labels
like Alpha
or Beta. These milestones will be called AM1, AM2, AM3, because we
need a letter that's ascii-wise a lower value that Final & GA.

Previously, I had said that you need to *check in your local changes*
(to your local github clone, not to origin!)
in order to ensure that those local changes are seen as "newer" than
the stuff available on download.jboss.org, or in your ~/.m2/repo.

This is no longer true -- a dirty github workspace will still result
in upversioned plugin timestamps. I believe this should even work
across timezones, since the plugins I built appear to be timestamped
in GMT, not EST.

Anyway, thanks for reading this far. The PRs in JBIDE-13671 have been
applied, and fresh CI builds should be available tomorrow.

Ref: https://issues.jboss.org/browse/JBIDE-13671


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com