I have n projects:
project_super: Aggregates the projects project_subi. Just a "pom-project".
project_sub1 : Inherits project_super
...
project_subi : Inherits project_super
...
roject_subn : Inherits project_super
1)
Most projects project_subi have an assembly descriptor sited in their
${basedir}\src\main\resources-build directories. They are identical. As n
gets big, these identical files will proliferate with the maintenance
overhead following. I guess this file could be "stored/defined" in
project_super and referred to by project_subi. How do I achieve this
conforming to best practices?
2)
Moreover, most project_subi uses this assembly descriptor in an identical
way, i.e. using the "maven-assembly-plugin". The plugin definitions are
identical. I.e. each project_subi pom contains exactly:
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>
<executions>
<execution>
<id>Package installation archive...</id>
<phase>pre-integration-test</phase>
<configuration>
<descriptors>
<descriptor>${basedir}/src/main/resources-build/assembly.descriptor.installation.archive.xml</descriptor>
</descriptors>
<finalName></finalName>
<outputDirectory>target</outputDirectory>
<workDirectory>target</workDirectory>
</configuration>
<goals>
<goal>assembly</goal>
</goals>
</execution>
</executions>
</plugin>
...
Could this somehow be defined in project_super and be referred to (run) by
the relevant projects project_subi?
--
View this message in context:
http://maven.40175.n5.nabble.com/Where-do-I-put-non-java-project-common-files-tp401369p401369.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
