Nils,
The "qualifier" in the version number is currently completely ignored. The one
special case that exists at the moment is indeed this "undefined development
version", which is the case when your version number starts with ${, i.e if you
use <version>${project.version}</version>, rely on Maven's processing of this
file, and that your dev.env. is setup to NOT process resources (which can be a
pita for a ton of other reasons). We could potentially use the -SNAPSHOT
qualifier to make the current version an "undefined development version".
I suspect that Openmind's special tasks/version handlers use this feature. I am
personally not convinced how best to treat this. It's convenient if files get
re-bootstrapped during dev, but then again, there are cases where I modify my
configuration (for example) and I DO NOT want to lose those changes after a
restart.
What do you have in mind ? How would you like your "snapshots" to be treated ?
-g
On 20 Jan 2011, at 12:03, Nils Breunese wrote:
>
> Hello,
>
> Does anything like Maven's SNAPSHOT versions exist for Magnolia modules?
> Looking at Magnolia's Version class there does seem to be some code for
> development versions although I can't find any code which uses this.
>
> Nils.
> ------------------------------------------------------------------------
> VPRO www.vpro.nl
> ------------------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
