Hi Daniel, > One of the simple options to solve the problem is to use a profile. its > very > likely that custom built distributions are built with: > mvn package or mvn install > and not > mvn package -P release-profile > and you could still issue a warning in the pom as xml comment, to not do > that and giving the reasons. In the profile configuration can be whatever > change to the build procedure you'd like (version file, ant-style filtering > of classes or ressources, whatever). While it's not fail proof I think it > would solve the problem nicely and without requiring too much thinking > during the build process (which I definitely like: "did you do A before you > did B and shipped the thing to be dropped on production servers" > immediately > followed by a wail of despair ;) > > Would that solve the problem or is a more secure solution necessary?
I like that approach. The concept has similarities with a local properties file, and is more general as it allows even actions to be modified. I'll keep that in mind when I think about the versioning problem in the future. thanks, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
