I thought the whole point of switching to the jgit timestamp provider is
that we'd see when the plugins were ACTUALLY changed, rather than being
forced to artificially bump them up.
-1 for fake commits just to bump the timestamp. A rebuild should change
nothing but the build ID (build timestamp + build number).
+1 for re-releasing the bits as 1.1.0.Final, with the corrected
index.html ("Stable Release" not "Nightly Build")
On 10/22/2013 03:58 AM, Mickael Istria wrote:
On 10/22/2013 09:32 AM, Max Rydahl Andersen wrote:
> Care to do a release that fixes this
Ok.
> and by consequence also gets new timestamp that should be never than
> anything else ? :)
It wouldn't have new timestamps by default as timestamps are computed
from the last commit on the given module. As the change of Locus version
don't change anything inside modules, it won't create new timestamps.
This requires a dummy commit on each module, which is not very nice.
Anyway, I'll make this commit to have newer timestamp and release
1.1.0.Final today.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com