Not a bad idea.
I'm +1 on making war/ear names fall into line with jar naming conventions, but -1 on having this in the project descriptor - no other deliverables are at this point, and I'd rather be consistent. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers "Alef Arendsen" To: "Turbine Maven Developers List (E-mail)" <alef@smarthav <[EMAIL PROTECTED]> en.com> cc: Subject: WAR and EAR names 05/21/02 07:02 PM Please respond to "Turbine Maven Developers List" Hi all, shouldn't the names of the war files and the ear files be the same as the projectname, including a version or something (just like the creation of the jar files). So shouldn't it be defined in the project descriptor instead of in the properties file? This way you have to override the properties in every project that generates an ear or war file. alef ====================================== Alef Arendsen [EMAIL PROTECTED] SmartHaven B.V. www.smarthaven.com Arlandaweg 92 M: +31 6 19 338 921 1043 EX Amsterdam T: +31 20 586 90 57 Netherlands F: +31 84 882 26 39 ====================================== -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
