Hilco Wijbenga-3 wrote: > > Why would this make it less repeatable? A build's > repeatability/reproducibility is based on the whether it is > deterministic. And whether a property can be overwritten/changed > doesn't change the determinism of a process. If it did, then (single > threaded) programming would be a lot harder... :-) >
In my case the property is changed by Groovy expression meaning it can take any value at run-time, as a regular application (something that Maven doesn't like to be, imo, with its focus on repeatability). For me it's not an issue at all, but for others this behavior may look like something that varies at run-time, less predictable and, therefore, less repeatable. I'll go even further, the POM I run where I have this issue isn't a regular job building some jars, it is a long process of actions resulting in all sorts of binaries created. Some data is downloaded from FTP servers and when FTP servers contain no new files, no binaries are created at all. Next time you run the same POM, FTP contain updates and binaries are created. Next time they are created or not, we don't know and don't care. Repeatability of builds is something we don't need in this case, like we don't need it when running any kind of background batch processing. We don't like it when it fails but when it works - any result is totally Ok and we expect them to be different on each run. So may be using Maven for this kind of batch processing and not as a "build tool" contradicts some of its philosophies a little. ----- Best regards, Evgeny http://evgeny-goldin.com/ evgeny-goldin.com -- View this message in context: http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-tp3360336p3362266.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
