what aspect of maven do you think is killing this use case?
1.2.3.4-SNAPSHOT when its run through the release process will offer up as a default 1.2.3.5-SNAPSHOT as the new development version and 1.2.3.4 as the released version... deployment will work...whats killing this for you? and the release process will let you change that if it doesn't guess right... jesse On 7/19/07, Johan Iskandar <[EMAIL PROTECTED]> wrote:
> From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > ok, I am a bit confused by what your actually asking here... > > but there is no reason in the world you can't use w.x.y.z versioning... > Well, since maven's main idea is to promote conventions.. and these conventions is there to ease and straighten out development process, why not take it to this level of detail..? It would ease versioning path details out of the developers mind.. Best regards, Johan
-- jesse mcconnell [EMAIL PROTECTED]
