Set a property based on the maven.build.timestamp

[JeneJasper]

The maven.build.timestamp property does not allow for timezone overrides for obvious reasons.

The timestamp-property goal can be used to create one with a local timezone timestamp. But the default implementation uses the current time, which is thus not the same for all modules in a multi module project.

The new timeSource parameter with value build now allows the usage of maven.build.timestamp property instead of the current timestamp.

[stefanseifert]

fixed by #32

[garretwilson]

Can someone explain the behavior of these two options, current and build? I'm not understanding what they do. I can guess what "current" means—probably something like Instant.now(). But where would the "build" time come from? If we're in the middle of the build, how could it be any different than "current"?

[garretwilson]

Oh, looking at the source code, the "build" source simply returns the time the entire build started, thus allowing all modules to have a consistent time. Is that a correct interpretation?