we just have to
decide if update occurs never/always, but I think we just need to
define a behavior which is consistent with the one used for snapshots
versions. Should be pretty trivial to do, I'll check carefully what
happens now and try to put a definitive solution in...
Well, with snapshot versions, you have at least a version *number*,
so you have the ability to at least some minimal decision. With the
${p.v}, you have *nothing*; as it is, everytime you restart, the
update mechanism is triggered, which is of course unacceptable.
If ${p.v} works but does never trigger an update (or additional
install) this is very much fine for me. I agree to Fabrizio that the
lesser pitfalls we have the better it is.
By the way this is not that much an eclipse problem I think. If you
ran magnolia directly in your IDE you might run into the exactly same
issues. So don't blame my development environment ;-)
Philipp Bracher
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
