[Engine-devel] [ATN] moving dbscripts location
Hello All, During the work I am doing to clean up the build of upcoming 3.3, I am going to move[1] dbscripts directory from: backend/manager/dbscripts to: packaging/dbscripts The packaging directory is a new directory established for files we copy as-is to installation media, dbscripts was the last remaining directory of that nature. dbscripts does not really belong to the java sources nor to required for java project build (except few validation that were kept). The packaging directory has the following advantages: 1. Simplify the build system to blindly copy files recursively from packaging to installation media. 2. Do not copy unnecessary files as we copy today, example is pom.xml. 3. Allow easy split plain files within packaging directory to sub packages in future. 4. Easier to understand the target system file layout by browsing the packaging directory, no magic of renaming or on the fly creation. 5. A clear separation between the maven build and the packaging build. Regards, Alon Bar-Lev. [1] http://gerrit.ovirt.org/#/c/15743
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "engine-devel" <engine-devel@ovirt.org> Cc: "Eli Mesika" <emesika@redhat.com> Sent: Monday, June 17, 2013 11:24:20 AM Subject: [ATN] moving dbscripts location
Hello All,
During the work I am doing to clean up the build of upcoming 3.3, I am going to move[1] dbscripts directory from: backend/manager/dbscripts to: packaging/dbscripts
The packaging directory is a new directory established for files we copy as-is to installation media, dbscripts was the last remaining directory of that nature. dbscripts does not really belong to the java sources nor to required for java project build (except few validation that were kept).
The packaging directory has the following advantages:
1. Simplify the build system to blindly copy files recursively from packaging to installation media.
2. Do not copy unnecessary files as we copy today, example is pom.xml.
3. Allow easy split plain files within packaging directory to sub packages in future.
4. Easier to understand the target system file layout by browsing the packaging directory, no magic of renaming or on the fly creation.
5. A clear separation between the maven build and the packaging build.
Regards, Alon Bar-Lev.
Hi I had reviewed that patch and it seems that it can be merged ASAP. +1 for merging that
Hello, This change was committed. Reminder: Database scripts were moved from: backend/manager/dbscripts to: packaging/dbscripts Regards, Alon Bar-Lev. ----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Monday, June 17, 2013 11:24:20 AM Subject: [Engine-devel] [ATN] moving dbscripts location
Hello All,
During the work I am doing to clean up the build of upcoming 3.3, I am going to move[1] dbscripts directory from: backend/manager/dbscripts to: packaging/dbscripts
The packaging directory is a new directory established for files we copy as-is to installation media, dbscripts was the last remaining directory of that nature. dbscripts does not really belong to the java sources nor to required for java project build (except few validation that were kept).
The packaging directory has the following advantages:
1. Simplify the build system to blindly copy files recursively from packaging to installation media.
2. Do not copy unnecessary files as we copy today, example is pom.xml.
3. Allow easy split plain files within packaging directory to sub packages in future.
4. Easier to understand the target system file layout by browsing the packaging directory, no magic of renaming or on the fly creation.
5. A clear separation between the maven build and the packaging build.
Regards, Alon Bar-Lev.
[1] http://gerrit.ovirt.org/#/c/15743 _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (2)
-
Alon Bar-Lev -
Eli Mesika