Fixed build error due to Update 2-12-20 related to log4j.

[vemedara]

1. Fixed build error due to Update 2-12-20 related to log4j
2. Updated pom.xml to generate build number based on git revision instead from svn.

[fat-tire]

Thanks! Hopefully this addresses @rae0506 issue #6. If they can confirm, I'll merge this in.

[fat-tire]

No confirmation from anyone. I can't build this atm but it's been almost a year now so I'm going to accept it and update to 2.17.1 due to concerns about vulns in log4j.

[rae0506]

Will try ASAP. Thanks for the update a d hard work. I appreciate it El mar., 4 ene. 2022 1:42 a. m., Fattire ***@***.***> escribió:

…

No confirmation from anyone. I can't build this atm but it's been almost a year now so I'm going to accept it and update to 2.17.1 due to concerns about vulns in log4j. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANL5TXQ57WI6J2ZY4VYNM6TUUKQH7ANCNFSM4ZR4L5AA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>