late last night I, Mark Lundquist wrote:
thinking about it some more, maybe the version to use should be specified as a suffix to be applied to whatever the model-determined artifact ID would otherwise be. That's the only reasonable way to be able to apply this to an aggregate of modules instead of having to specify a version separately for each module (because, e.g. in Cocoon, there is no longer a single project-wide version "wavefront", we have a core+plugins organization now and different things may be on different release schedules... and it is maybe still desirable from a local repo mgmt POV to have the normal artifact version recognizable within the local build-specific version).
nah... on second thought, the prefix idea is too fiddly. I really don't give a crap about the normal version ID or having the private version ID being related to it. So, my private, build-local version ID should just be "foobar" or "JIRA-1234" or whatever.
So, any thoughts about this idea? cheers, —ml— --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
