[Glass] Jade - local monticello repositories -no new revisions possible ...

[itlists at schrievkrom.de]

Am 14.11.2013 14:20, schrieb James Foster:
> Martin,
> 
> Jade does attempt to be somewhat “clever” and if it thinks that the package has not been modified then it will not let you edit the version number. You can save the package to a different repository, but not to the same one. Sometimes things are changed in the package but Jade didn’t notice. Some possible paths:
> 
> (1) A work-around is to make a trivial edit to some method (add a space to the end of a line), and see if the package is marked dirty. If so, then the save process should allow a new version.

 No, that does not change it - though Jade knows now (after changing a
method), that there are changes (when I compare the current version
against my oldest version "4") and it shows the correct changes.

 The modified flag of the package is not modified.

> (2) Figure how how the package changed without Jade noticing and let me know and I’ll fix it. If the package has changed, then Jade should recognize it!

 Seems for me, that the version changes are using the Announcement stuff
(?) and this does not work any more in my package ...


> (3) Remove the “feature” of not letting you modify the version of an unmodified package. If you want to be able to change the version on an unmodified package, let me know the reason/use case and we can tell Jade to relax.

 Well, the user should decide - even in ENVY you can create a new
edition and then version it again.


Marten