It looks like we just need to add a zipfileset for the *.sh files and use the filemode attribute with the exec bit set. This should work with "most unixes"; we'll test on solaris, linux & hp.
http://ant.apache.org/manual/CoreTypes/zipfileset.html Otherwise, we'll use native zip. For the record, we do build on unix. I guess this hasn't been an issue up until now because most folks used tar.gz on unix, as did I. -----Original Message----- From: Dimitris Andreadis Sent: Friday, May 05, 2006 7:30 AM To: Mladen Turk Cc: Scott M Stark; QA; jboss-development@lists.sourceforge.net Subject: RE: FW: 4.0.4.CR2 distribution (.zip only?) I tested it too, so if we zip with /usr/bin/zip the produced zip file maintains the file permissions, as long as you unzip with /usr/bin/unzip. If you use the 'jar' utility, the permission are lost when zipping, and also ignored when unzipping (if they were put there by /usr/bin/zip). So a solution would be to A) Make sure the jboss bin .sh file have the correct permissions, or 'chmod ugo+rx $JBOSS_HOME/bin/*.sh' (since those are set in the bin-tgz target, etc.) B) zip with the external utility, e.g.: /usr/bin/zip -9qr jboss-4.0.4.GA.zip jboss-4.0.4.GA/ C) Document that the user needs to either use the zip utility on unix, or jar -xvf and chmod yourself. Can someone from QA comment? ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
