Stefan Prange wrote:
yes there is. Our operations team defined this convention. Their deploy script looks for ear files that are named after this pattern. But the timestamp part after the "appname.ear_" is completely arbitrary. It's meant to be a version marker to distinguish different EAR files. The deploy script always picks the EAR file with the most recent file date (i.e. the date which can be updated by using "touch".)
Sounds way easier to get the operations team from changing their mask from appname.ear_* to appname-*.ear.
It sounds silly to forego a lot of useful functionality because a filename is the wrong way around.
Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
