Re: Ant Build Distribution System
OK, now I've added the same distribution funcionality to sdo project...an example of distribution task working on sdo project can be found here: [1]...of course it was necessary some minor changes on distribution task to fit on sdo project : ) Now, I think if everybody is ok with it, we could add this task also to sca subproject, otherwise, I will need some help with it, cause sca structure is a bit more complicated and I'm not used to...can you help me with that Brady? Adriano Crestani [1] http://people.apache.org/~adrianocrestani/sdo_distribution_example/http://people.apache.org/%7Eadrianocrestani/sdo_distribution_example/ On Nov 28, 2007 10:20 PM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, Sorry for the long time being inactive, but I'm back : ) I've got the ant build distribution generator signing correctly the packed files. I first tried out to call directly gpg using the exec task, but, unfortunately, during the gpg signing process it requires the password for the secret key to be input, otherwise, the exec task does not allow any input during its execution. So, I looked for another solution, and found the Apache Commons OpenPGP project that provides an ant task just to sign files using the gpg, then I compiled it and the generated the OpenPGP.jar that was added to das/antscripts/ folder. The OpenPGP.jar requires another 2 jars(described below) that should be download manually, I think it's ok, once OpenPGP.jar will only be used to sign the distributions and will not be included on the distributed files. Below the usage instructions, that was added to READ_ANT_INSTALL file, of the ant auto distribution system: GENERATING A PROJECT DISTRIBUTION = To create a src and bin distribution of Tuscany DAS subproject, there must be set some properties on platform.properties files: Property Required Example Description --- --- platform.public.key.path Yes E:/gnupg/trustdb.gpg The public key ring file path platform.secret.key.path Yes E:/gnupg/secring.gpg The secret key ring file path platform.key.id Yes 148CAFB2 The key id used to sign the distribution files platform.tuscanyDAS.distribution.dir NO C:\distribution\ The folder where the distribution files will be generated, default=tuscanyDAS.root.dir/distribution platform.tuscanyDAS.release.file.name NO tuscany_das_native-1.0-incubator-M4- The beginning of src and bin packed distribution file name, default=tuscany_cpp_das. TUSCANY_DASCPP_RELEASE_NAME env var may be used as an alternative Also is required the bcpg-jdklatest_version-latest_version.jar and jce-jdklatest_version-latest_version.jar files defines on classpath. Both can be found at http://www.bouncycastle.org/latest_releases.html Use the distribution target to generate the src and bin distribution file structure under platform.tuscanyDAS.distribution.dir folder. Then use the pack.distribution target to pack the bin and src distribution folders as .zip and .tar.gz and generate their .asc and .md5 files. A password must be set on the command line when using pack.distributiontarget, this password is used to sign the packed distribution files with the secret key defined on platform.secret.key.path Usage: ant distribution // do whatever you want on the generated distribution files ant pack.distribution -Dpassword=123456 The bad point in this system is that you have to type your password on command line, a bad practice once shells usually have a log file of all typed commands. I thought about a file, which contains the password, then the ant could read the password from this file...this way the password would not be typed on the command line, but I think it's a lot of work just to set a password :S...suggestions??? I have also updated the distribution example on [1]. I think next step is to create the NOTICE, LICENSE...files for das that are still missing :P [1] http://people.apache.org/ http://tr_1196323527526 ~adrianocrestani/das_distributi http://tr_1196323527526on_example/http://people.apache.org/%7Eadrianocrestani/das_distribution_example/%20 On Nov 14, 2007 1:10 AM, ant elder [EMAIL PROTECTED] wrote: On Nov 14, 2007 7:29 AM, Adriano Crestani [EMAIL PROTECTED] wrote: snip Luciano: Distribution artifact names : I'd follow the same naming of previous native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip I'm also not sure if the native project wants to start using incubating in the name, to follow the same pattern being used in the java releases. I think its currently incubating thats prefered these days,
Re: Ant Build Distribution System
Hi, Sorry for the long time being inactive, but I'm back : ) I've got the ant build distribution generator signing correctly the packed files. I first tried out to call directly gpg using the exec task, but, unfortunately, during the gpg signing process it requires the password for the secret key to be input, otherwise, the exec task does not allow any input during its execution. So, I looked for another solution, and found the Apache Commons OpenPGP project that provides an ant task just to sign files using the gpg, then I compiled it and the generated the OpenPGP.jar that was added to das/antscripts/ folder. The OpenPGP.jar requires another 2 jars(described below) that should be download manually, I think it's ok, once OpenPGP.jar will only be used to sign the distributions and will not be included on the distributed files. Below the usage instructions, that was added to READ_ANT_INSTALL file, of the ant auto distribution system: GENERATING A PROJECT DISTRIBUTION = To create a src and bin distribution of Tuscany DAS subproject, there must be set some properties on platform.properties files: Property Required Example Description --- --- platform.public.key.path Yes E:/gnupg/trustdb.gpg The public key ring file path platform.secret.key.path Yes E:/gnupg/secring.gpg The secret key ring file path platform.key.id Yes 148CAFB2 The key id used to sign the distribution files platform.tuscanyDAS.distribution.dir NO C:\distribution\ The folder where the distribution files will be generated, default=tuscanyDAS.root.dir/distribution platform.tuscanyDAS.release.file.name NO tuscany_das_native-1.0-incubator-M4- The beginning of src and bin packed distribution file name, default=tuscany_cpp_das. TUSCANY_DASCPP_RELEASE_NAME env var may be used as an alternative Also is required the bcpg-jdklatest_version-latest_version.jar and jce-jdklatest_version-latest_version.jar files defines on classpath. Both can be found at http://www.bouncycastle.org/latest_releases.html Use the distribution target to generate the src and bin distribution file structure under platform.tuscanyDAS.distribution.dir folder. Then use the pack.distribution target to pack the bin and src distribution folders as .zip and .tar.gz and generate their .asc and .md5 files. A password must be set on the command line when using pack.distributiontarget, this password is used to sign the packed distribution files with the secret key defined on platform.secret.key.path Usage: ant distribution // do whatever you want on the generated distribution files ant pack.distribution -Dpassword=123456 The bad point in this system is that you have to type your password on command line, a bad practice once shells usually have a log file of all typed commands. I thought about a file, which contains the password, then the ant could read the password from this file...this way the password would not be typed on the command line, but I think it's a lot of work just to set a password :S...suggestions??? I have also updated the distribution example on [1]. I think next step is to create the NOTICE, LICENSE...files for das that are still missing :P [1] http://people.apache.org/ tr_1196323527526 ~adrianocrestani/das_distributi tr_1196323527526on_example/http://people.apache.org/%7Eadrianocrestani/das_distribution_example/%20 On Nov 14, 2007 1:10 AM, ant elder [EMAIL PROTECTED] wrote: On Nov 14, 2007 7:29 AM, Adriano Crestani [EMAIL PROTECTED] wrote: snip Luciano: Distribution artifact names : I'd follow the same naming of previous native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip I'm also not sure if the native project wants to start using incubating in the name, to follow the same pattern being used in the java releases. I think its currently incubating thats prefered these days, incubator was an older one. [1] http://people.apache.org/dist/incubator/tuscany/cpp/1.0-incubator-M2/win32/ Sorry, I have added a new property on plataform.properties file that defines the distribution file name, I just forgot to set it before pack the distribution files, then it used the default value that is tuscany_das_cpp. But, I will be using tuscany_das_cpp-1.0-incubator-M4-type.extension naming pattern, following the last sdo and sca cpp release. Release artifact names : Should DLL and other artifacts have incubator/incubating on their names ? So, tuscany_das.dll would become tuscany-das-1.0-incubator-M4.dll I was just following the last cpp bin releases. So, I think I'm not the right person to answer that. But for me, it's ok to keep tuscany_das.dll ;
Re: Ant Build Distribution System
On Nov 14, 2007 7:29 AM, Adriano Crestani [EMAIL PROTECTED] wrote: snip Luciano: Distribution artifact names : I'd follow the same naming of previous native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip I'm also not sure if the native project wants to start using incubating in the name, to follow the same pattern being used in the java releases. I think its currently incubating thats prefered these days, incubator was an older one. [1] http://people.apache.org/dist/incubator/tuscany/cpp/1.0-incubator-M2/win32/ Sorry, I have added a new property on plataform.properties file that defines the distribution file name, I just forgot to set it before pack the distribution files, then it used the default value that is tuscany_das_cpp. But, I will be using tuscany_das_cpp-1.0-incubator-M4-type.extension naming pattern, following the last sdo and sca cpp release. Release artifact names : Should DLL and other artifacts have incubator/incubating on their names ? So, tuscany_das.dll would become tuscany-das-1.0-incubator-M4.dll I was just following the last cpp bin releases. So, I think I'm not the right person to answer that. But for me, it's ok to keep tuscany_das.dll ; ) The things that need to include incubating in the name are the artiacts that will be distributed individually somewhere , so the binary and src distributions do as they're on the download page, in Java all the jars that go in the the maven repository need it which is why all the sca/module jars have it but the sca/samples don't, so if the .dll's are available somewhere outside of the binary distribution they need it otherwise probably not. ...ant
Re: Ant Build Distribution System
I've had a quick look, these look pretty good to me. There are a few standard Apache files that you need to add, all distributions should have LICENSE, NOTICE, README and RELEASE_NOTES files, and src distributions should have a BUILDING file, bin distributions an INSTALL file. You can see some examples at https://svn.apache.org/repos/asf/incubator/tuscany/java/das/distribution/source/or https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/distribution/src/main/release/ . I'd use hyphens instead of underscores in the names, eg tuscany-das-cppsrc, not sure if there's any conventions on this so if you prefer underscores thats probably fine. ...ant On Nov 13, 2007 6:15 AM, Adriano Crestani [EMAIL PROTECTED] wrote: As Luciano suggested, I've placed the generated distribution example on my p.a.o account: http://people.apache.org/~adrianocrestani/das_distribution_example/http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ Adriano Crestani On Nov 12, 2007 2:12 PM, Adriano Crestani [EMAIL PROTECTED] wrote: I've added a distribution example of what is being generated by the distribution and pack.distribution targets on my sandbox [1]. - src and bin dirs are generated by distribution target - the .zip, .tar.gz, .md5 and .asc(still working on it) are being generated by pack.distribution targets from the bin and src dirs - there is still no NOTICE, COPYRIGHT, README AND LICENSE files cause I haven't added them yet [1] https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/crestani Adriano Crestani On Nov 11, 2007 10:10 PM, Luciano Resende [EMAIL PROTECTED] wrote: If you could post a sample distro in your p.a.o account, it would make it easier for others to review, at least for those that does not have all the native environment setup. On Nov 11, 2007 9:19 PM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, On revision 594022 I've added new targets: distribution and pack.distribution on DAS ant build system. distribution target creates a distribution file structure for both, src and bin distribution. pack.distribution target packs the generated distribution files and generates the .md5 and .asc( still working on it ) files. I've also updated the ANT_README_AND_INSTALL file with the description of these new targets. I'd like someone else could revise the distribution structure that these new targets are creating and give some suggestions. Then, after everything is ok with these new targets, we could reapply it to SDO and SCA projects. Thoughts? Suggestions? Adriano Crestani -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant Build Distribution System
Couple more comments : Distribution artifact names : I'd follow the same naming of previous native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip I'm also not sure if the native project wants to start using incubating in the name, to follow the same pattern being used in the java releases. [1] http://people.apache.org/dist/incubator/tuscany/cpp/1.0-incubator-M2/win32/ Release artifact names : Should DLL and other artifacts have incubator/incubating on their names ? So, tuscany_das.dll would become tuscany-das-1.0-incubator-M4.dll Signatures : Not sure if these are suposed to be ready yet, but i tried to verify them and got the following error D:\temp\das-cppgpg --verify tuscany_das_cppbin.zip.asc gpg: no valid OpenPGP data found. gpg: the signature could not be verified. I guess we will have more comments once the LEGAL files are in place (e.g LICENSE and NOTICE). On Nov 13, 2007 1:09 AM, ant elder [EMAIL PROTECTED] wrote: I've had a quick look, these look pretty good to me. There are a few standard Apache files that you need to add, all distributions should have LICENSE, NOTICE, README and RELEASE_NOTES files, and src distributions should have a BUILDING file, bin distributions an INSTALL file. You can see some examples at https://svn.apache.org/repos/asf/incubator/tuscany/java/das/distribution/source/or https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/distribution/src/main/release/ . I'd use hyphens instead of underscores in the names, eg tuscany-das-cppsrc, not sure if there's any conventions on this so if you prefer underscores thats probably fine. ...ant On Nov 13, 2007 6:15 AM, Adriano Crestani [EMAIL PROTECTED] wrote: As Luciano suggested, I've placed the generated distribution example on my p.a.o account: http://people.apache.org/~adrianocrestani/das_distribution_example/http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ Adriano Crestani On Nov 12, 2007 2:12 PM, Adriano Crestani [EMAIL PROTECTED] wrote: I've added a distribution example of what is being generated by the distribution and pack.distribution targets on my sandbox [1]. - src and bin dirs are generated by distribution target - the .zip, .tar.gz, .md5 and .asc(still working on it) are being generated by pack.distribution targets from the bin and src dirs - there is still no NOTICE, COPYRIGHT, README AND LICENSE files cause I haven't added them yet [1] https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/crestani Adriano Crestani On Nov 11, 2007 10:10 PM, Luciano Resende [EMAIL PROTECTED] wrote: If you could post a sample distro in your p.a.o account, it would make it easier for others to review, at least for those that does not have all the native environment setup. On Nov 11, 2007 9:19 PM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, On revision 594022 I've added new targets: distribution and pack.distribution on DAS ant build system. distribution target creates a distribution file structure for both, src and bin distribution. pack.distribution target packs the generated distribution files and generates the .md5 and .asc( still working on it ) files. I've also updated the ANT_README_AND_INSTALL file with the description of these new targets. I'd like someone else could revise the distribution structure that these new targets are creating and give some suggestions. Then, after everything is ok with these new targets, we could reapply it to SDO and SCA projects. Thoughts? Suggestions? Adriano Crestani -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant Build Distribution System
There are a few standard Apache files that you need to add, all distributions should have LICENSE, NOTICE, README and RELEASE_NOTES files, and src distributions should have a BUILDING file, bin distributions an INSTALL file. You can see some examples at https://svn.apache.org/repos/asf/incubator/tuscany/java/das/distribution/source/or https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/distribution/src/main/release/ This files were not included on distribution files, because they do not exist yet, but will be created soon ; ) Ant: I'd use hyphens instead of underscores in the names, eg tuscany-das-cppsrc, not sure if there's any conventions on this so if you prefer underscores thats probably fine. Luciano: Distribution artifact names : I'd follow the same naming of previous native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip I'm also not sure if the native project wants to start using incubating in the name, to follow the same pattern being used in the java releases. [1] http://people.apache.org/dist/incubator/tuscany/cpp/1.0-incubator-M2/win32/ Sorry, I have added a new property on plataform.properties file that defines the distribution file name, I just forgot to set it before pack the distribution files, then it used the default value that is tuscany_das_cpp. But, I will be using tuscany_das_cpp-1.0-incubator-M4-type.extension naming pattern, following the last sdo and sca cpp release. Release artifact names : Should DLL and other artifacts have incubator/incubating on their names ? So, tuscany_das.dll would become tuscany-das-1.0-incubator-M4.dll I was just following the last cpp bin releases. So, I think I'm not the right person to answer that. But for me, it's ok to keep tuscany_das.dll ; ) Signatures : Not sure if these are suposed to be ready yet, but i tried to verify them and got the following error D:\temp\das-cppgpg --verify tuscany_das_cppbin.zip.asc gpg: no valid OpenPGP data found. gpg: the signature could not be verified. Yes, you should get this message, because I'm still working on the auto generation of .asc files. Thanks for the replies : ) Adriano Crestani On Nov 13, 2007 10:01 AM, Luciano Resende [EMAIL PROTECTED] wrote: Couple more comments : Distribution artifact names : I'd follow the same naming of previous native releases [1] and use tuscany_das_cpp-1.0-incubator-M4-bin.zip I'm also not sure if the native project wants to start using incubating in the name, to follow the same pattern being used in the java releases. [1] http://people.apache.org/dist/incubator/tuscany/cpp/1.0-incubator-M2/win32/ Release artifact names : Should DLL and other artifacts have incubator/incubating on their names ? So, tuscany_das.dll would become tuscany-das-1.0-incubator-M4.dll Signatures : Not sure if these are suposed to be ready yet, but i tried to verify them and got the following error D:\temp\das-cppgpg --verify tuscany_das_cppbin.zip.asc gpg: no valid OpenPGP data found. gpg: the signature could not be verified. I guess we will have more comments once the LEGAL files are in place (e.g LICENSE and NOTICE). On Nov 13, 2007 1:09 AM, ant elder [EMAIL PROTECTED] wrote: I've had a quick look, these look pretty good to me. There are a few standard Apache files that you need to add, all distributions should have LICENSE, NOTICE, README and RELEASE_NOTES files, and src distributions should have a BUILDING file, bin distributions an INSTALL file. You can see some examples at https://svn.apache.org/repos/asf/incubator/tuscany/java/das/distribution/source/or https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/distribution/src/main/release/ . I'd use hyphens instead of underscores in the names, eg tuscany-das-cppsrc, not sure if there's any conventions on this so if you prefer underscores thats probably fine. ...ant On Nov 13, 2007 6:15 AM, Adriano Crestani [EMAIL PROTECTED] wrote: As Luciano suggested, I've placed the generated distribution example on my p.a.o account: http://people.apache.org/~adrianocrestani/das_distribution_example/http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ Adriano Crestani On Nov 12, 2007 2:12 PM, Adriano Crestani [EMAIL PROTECTED] wrote: I've added a distribution example of what is being generated by the distribution and pack.distribution targets on my sandbox [1]. - src and bin dirs are generated by distribution target - the .zip, .tar.gz, .md5 and .asc(still working on it) are being generated by pack.distribution targets from the bin and src dirs - there is still no NOTICE, COPYRIGHT, README AND LICENSE files cause I haven't added them yet [1] https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/crestani
Re: Ant Build Distribution System
I've added a distribution example of what is being generated by the distribution and pack.distribution targets on my sandbox [1]. - src and bin dirs are generated by distribution target - the .zip, .tar.gz, .md5 and .asc(still working on it) are being generated by pack.distribution targets from the bin and src dirs - there is still no NOTICE, COPYRIGHT, README AND LICENSE files cause I haven't added them yet [1] https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/crestani Adriano Crestani On Nov 11, 2007 10:10 PM, Luciano Resende [EMAIL PROTECTED] wrote: If you could post a sample distro in your p.a.o account, it would make it easier for others to review, at least for those that does not have all the native environment setup. On Nov 11, 2007 9:19 PM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, On revision 594022 I've added new targets: distribution and pack.distribution on DAS ant build system. distribution target creates a distribution file structure for both, src and bin distribution. pack.distribution target packs the generated distribution files and generates the .md5 and .asc( still working on it ) files. I've also updated the ANT_README_AND_INSTALL file with the description of these new targets. I'd like someone else could revise the distribution structure that these new targets are creating and give some suggestions. Then, after everything is ok with these new targets, we could reapply it to SDO and SCA projects. Thoughts? Suggestions? Adriano Crestani -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant Build Distribution System
As Luciano suggested, I've placed the generated distribution example on my p.a.o account: http://people.apache.org/~adrianocrestani/das_distribution_example/http://people.apache.org/%7Eadrianocrestani/das_distribution_example/ Adriano Crestani On Nov 12, 2007 2:12 PM, Adriano Crestani [EMAIL PROTECTED] wrote: I've added a distribution example of what is being generated by the distribution and pack.distribution targets on my sandbox [1]. - src and bin dirs are generated by distribution target - the .zip, .tar.gz, .md5 and .asc(still working on it) are being generated by pack.distribution targets from the bin and src dirs - there is still no NOTICE, COPYRIGHT, README AND LICENSE files cause I haven't added them yet [1] https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/crestani Adriano Crestani On Nov 11, 2007 10:10 PM, Luciano Resende [EMAIL PROTECTED] wrote: If you could post a sample distro in your p.a.o account, it would make it easier for others to review, at least for those that does not have all the native environment setup. On Nov 11, 2007 9:19 PM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, On revision 594022 I've added new targets: distribution and pack.distribution on DAS ant build system. distribution target creates a distribution file structure for both, src and bin distribution. pack.distribution target packs the generated distribution files and generates the .md5 and .asc( still working on it ) files. I've also updated the ANT_README_AND_INSTALL file with the description of these new targets. I'd like someone else could revise the distribution structure that these new targets are creating and give some suggestions. Then, after everything is ok with these new targets, we could reapply it to SDO and SCA projects. Thoughts? Suggestions? Adriano Crestani -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant Build Distribution System
If you could post a sample distro in your p.a.o account, it would make it easier for others to review, at least for those that does not have all the native environment setup. On Nov 11, 2007 9:19 PM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, On revision 594022 I've added new targets: distribution and pack.distribution on DAS ant build system. distribution target creates a distribution file structure for both, src and bin distribution. pack.distribution target packs the generated distribution files and generates the .md5 and .asc( still working on it ) files. I've also updated the ANT_README_AND_INSTALL file with the description of these new targets. I'd like someone else could revise the distribution structure that these new targets are creating and give some suggestions. Then, after everything is ok with these new targets, we could reapply it to SDO and SCA projects. Thoughts? Suggestions? Adriano Crestani -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
