If you put the properties higher in the pom, do they get filtered then? theres never really a clear "Schema" for what can go into "configuration" of a plugin and I don't see a reference to placing "properties" in the assembly plugin config

Instead you might also try:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/filtering-some-distribution-files.html

Mark

On Fri, Jul 29, 2011 at 7:18 AM, Mark H. Wood <mwood@iupui.edu> wrote:
Nobody on the Maven list has responded, so I'll annoy you all here.

In pom.xml (the top one, in dspace-parent):

<plugin>
 <artifactId>maven-assembly-plugin</artifactId>
 <executions>
   <execution>
     <phase>package</phase>
     <goals>
       <goal>single</goal>
     </goals>
     <configuration>
       <descriptors>
         <descriptor>src/main/assembly/testEnvironment.xml</descriptor>
       </descriptors>
       <properties>
         <!-- Values to filter into the test environment's configuration -->
         <default.db.name>oracle</default.db.name>
         <default.db.url>jdbc:h2:mem:test;MODE=Oracle</default.db.url>
         <default.db.driver>org.h2.Driver</default.db.driver>
         <default.db.username>sa</default.db.username>
         <default.db.password>sa</default.db.password>
         <default.mail.server>localhost</default.mail.server>
       </properties>
     </configuration>
   </execution>
 </executions>
 <inherited>false</inherited>
</plugin>

src/main/assembly/testEnvironment.xml:

<assembly
       xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd">
 <!--
      Package DSpace's common testing environment
      (configuration, etc.)
 -->
 <id>testEnvironment</id>
 <formats>
   <format>zip</format>
 </formats>
 <includeBaseDirectory>false</includeBaseDirectory>
 <moduleSets>
   <moduleSet>
     <sources>
       <outputDirectoryMapping>dspace</outputDirectoryMapping>
       <fileSets>
         <fileSet>
           <directory/>
           <outputDirectory/>
           <excludes>
             <exclude>config/dspace.cfg</exclude>
           </excludes>
           <includes>
             <include>config/**/*</include>
             <include>etc/**/*</include>
           </includes>
         </fileSet>
         <fileSet>
           <includes>
             <include>config/dspace.cfg</include>
           </includes>
           <filtered>true</filtered>
         </fileSet>
       </fileSets>
     </sources>
   </moduleSet>
 </moduleSets>
</assembly>

This picks up config/ and etc/ from every project and gloms them all
into a Zip archive, combining them into a single config/ and a single
/etc.  So far, so good.  However, dspace.cfg is not being filtered and
I don't see why.

I know there's no default.mail.server -- if I can make this work,
there will be.

What I want is that, when a project unpacks the Zip to use it as a
[DSpace] tree for the test phase, dspace.cfg should be set up to use
the test DBMS (and have other settings that will not cause surprise).

--
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
Asking whether markets are efficient is like asking whether people are smart.

------------------------------------------------------------------------------
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel




--
Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Esperantolaan 4 - Heverlee 3001 - Belgium