Arvind Prabhakar added a comment - 17/Jul/12 20:50 The current layout generates the following structure: . ├── bin │   └── sqoop.sh ├── client │   └── lib │   ├── ... │   └── sqoop-common-2.0.0-SNAPSHOT.jar └── server ├── LICENSE ├── NOTICE ├── RELEASE-NOTES ├── RUNNING.txt ├── bin │   ├── catalina.sh │   ├── ... │   ├── setenv.bat │   ├── setenv.sh │   └── ... ├── conf │   ├── catalina.properties │   ├── ... │   ├── sqoop.properties │   ├── sqoop_bootstrap.properties │   └── ... ├── lib │   ├── ... │   └── tomcat-util.jar ├── logs ├── temp │   └── safeToDelete.tmp ├── webapps │   ├── ROOT │   └── sqoop.war └── work This is very different from the source layout which is of the form: . ├── DISCLAIMER.txt ├── LICENSE.txt ├── NOTICE.txt ├── README.txt ├── client │   └── ... ├── common │   └── ... ├── connector │   └── ... ├── core │   └── ... ├── dist │   └── ... ├── docs │   └── ... ├── pom.xml ├── repository │   └── ... ├── server │   └── ... ├── spi │   └── ... └── target └── ... It will be good to follow the same source layout with added directories at the top to help make sure that top level files exist in the distribution at the necessary location among other benefits. One suggested layout would be as follows: . ├── DISCLAIMER.txt ├── LICENSE.txt ├── NOTICE.txt ├── README.txt ├── bin │   └── sqoop ├── client │   └── ... ├── common │   └── ... ├── config | ├── sqoop_bootstrap.properties │   └── sqoop.properties ├── connector │   └── ... ├── core │   └── ... ├── dist │   └── ... ├── docs │   └── ... ├── pom.xml ├── repository │   └── ... ├── server │   └── ... ├── spi │   └── ... ├── target |   └── ... ├── lib |   └── <all compiled libs> └── webserver    └── <tomcat specific files> With this layout the config files, bin scripts will remain in the top level directory and will be able to run directly form there. Also this distribution will be identical to the source distribution without the compiled binaries.

Jarek Jarcec Cecho added a comment - 18/Jul/12 07:27 Do we need to follow the same directory structure for binary artifact as is in source artifact? I kind of like this division present in binary artifact into client and server (and common bin) directory. I believe that it will be very easy for end user to simply take it and deploy it.

Arvind Prabhakar added a comment - 18/Jul/12 17:14 @Jarcec - typically most Hadoop related projects tend to create the binary distribution as a superset of source distribution. You could for example, take a release's binary distribution which contains sources and build it with any changes that you need. Sqoop 1 has had a similar layout for binary distribution in all its releases. The other aspect of this is that there are top-level files such as LICENSE, NOTICE, README etc which need to reside at the root of the distribution - much like they reside at the root of the source distribution as well. Having a bin distribution that includes the source distribution as well in it will keep things updated as and when these top-level files change.

Jarek Jarcec Cecho added a comment - 19/Jul/12 07:40 Thank you Arvind for your comment. Your arguments make sense to me. Jarcec

Bilung Lee added a comment - 13/Nov/12 18:54 Patch is in. Thanks.