Hi,
I´m thinking about where to put my DDL scripts in our project structure:
Actually we have two projects with DDL scripts as part of a multi-module
build.
project-core
\src\main\java
\conf\ddl
project-ext
\src\main\java
\conf\ddl
When the multi-module build gets released, only the *.jars (containing
*.class files) go to the mavenrepo - the \conf\ddl folders are'nt
versioned.
When the whole project gets delivered (in a special structure for the
customer), we have a separate "delivery build" which references the
release of the multi-module build,
the releases of some other sub-modules, a documentation folder and so on.
This "delivery-build" also references relative the \ddl folders of
"project-core" and "project-ext":
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>copy</id>
<phase>package</phase>
<configuration>
<tasks>
<copy
todir="${delivery_dir}/${productVersion}/Install/DB" flatten="true"
failonerror="true">
<fileset dir="
../../../system/backend/project-ext/conf/ddl">
<include
name="**/*"/>
</fileset>
<fileset dir="
../../../system/backend/project-core/conf/ddl">
<include
name="**/*"/>
<exclude
name="**/updatedb*"/>
</fileset>
<fileset
dir="../../../install/additional-db-scripts">
<include
name="**/update_db*"/>
</fileset>
</copy>
....
Now, I want to "release" the \conf\ddl folders too, as part of the
multi-module build and pack them into "project-core.zip" or
"project-ext.zip".
==> Would you suggest to have 2 artifacts within one module (one *.jar
artifact containing the source files and one artifact containing the DDL
files)
or separte the DDL files into a new sub-module (for example
project-core-ddl and project-ext-ddl) ?
Thanx for your advice,
Torsten
