[ 
https://issues.apache.org/jira/browse/OODT-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ross Laidlaw updated OODT-642:
------------------------------

    Skill Level: Newcomer (Easy) - Everyone can do this  (was: Don't Know 
(Unsure) - The default level)
    
> Move the CAS-Product test classes to src/test/java and the resources to 
> src/test/resources
> ------------------------------------------------------------------------------------------
>
>                 Key: OODT-642
>                 URL: https://issues.apache.org/jira/browse/OODT-642
>             Project: OODT
>          Issue Type: Test
>          Components: product server
>    Affects Versions: 0.6
>            Reporter: Ross Laidlaw
>            Assignee: Ross Laidlaw
>            Priority: Trivial
>              Labels: build, maven
>             Fix For: 0.6
>
>         Attachments: OODT-642.rlaidlaw.2013-07-08.patch.txt
>
>
> This update moves two test classes for the CAS-Product web application from 
> 'src/test' to 'src/test/java', and it moves one resource file from 
> 'src/testdata' to 'src/test/resources'.
> These changes are an attempt to bring the project structure closer to the 
> [standard directory layout for a Maven 
> project|http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html].
> This is a trivial change, it makes no Java code changes and simply moves 
> three items (two Java classes and one properties file).  But to support the 
> move, there are a couple of minor changes to the POM as shown below:
> {code:xml|title=pom.xml|borderStyle=solid}
> <build>
>   <testSourceDirectory>${basedir}/src/test/java</testSourceDirectory>
>   ...
>   <plugins>
>     <plugin>
>       <artifactId>maven-assembly-plugin</artifactId>
>       <configuration>
>         <systemProperties>
>           <property>
>             <name>java.util.logging.config.file</name>
>             <value>
>               ${basedir}/src/test/resources/test.logging.properties
>             </value>
>           </property>
>         </systemProperties>
>       </configuration>
>     </plugin>
>   </plugins>
> </build>
> {code}
> I'm not sure if the above moves can be captured by a patch.  Nevertheless, 
> I'll attach a patch made by running svn diff after all of the moves and POM 
> updates had been carried out locally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to