Scott Ryan wrote:
> We actually use the same application context but use the test resources 
> construct to pull it out of the main build path for use during testing.  You 
> just need to include the xml files from the main tree in your resources 
> during testing and it works very nice.  We use a different hibernate 
> configuration since in one case we are using a JNDI lookup in production and 
> during testing just a direct jdbc connection.  The xml is configured to build 
> the session factory from the data source we define in the properties file.  
> If you like I can send you the maven 1 or 2 config we are using.
>   
Can you please send me the m2 config? I don't understand what you mean
by "pull it out of the main build path".
> Scott Ryan
> Chief Technology Officer
> Soaring Eagle L.L.C.
> [EMAIL PROTECTED]
> www.soaringeagleco.com
> (303) 263-3044 
>
> -----Original Message-----
> From: Matt Raible [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 23, 2006 10:58 AM
> To: Maven Users List
> Subject: Re: Better to use variables or hard-coded paths?
>
>
> On 8/23/06, Daniel Serodio <[EMAIL PROTECTED]> wrote:
>   
>> Matt Raible wrote:
>>     
>>> I'm customizing my pom.xml so XML files are available on my classpath
>>> (at /WEB-INF/*.xml) when testing. My question is (hopefully) simple.
>>>
>>> Is it better to use:
>>>       
>> <snip/>
>>
>> I think using "Hard-coded directories" is more "Maven-like", while using
>> variables is more "Ant-like". I'd stick with the hard-coded directories,
>> or better yet, use Maven's "stardard directory layout"
>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>>     
>
> I am using this layout, I just need to include src/main/webapp in my
> classpath so I can use /WEB-INF/applicationContext.xml in my tests -
> w/o having duplicate context files.
>
> Thanks for your advice Daniel.
>
> Matt
>
>   
>> HTH,
>> Daniel Serodio
>>     


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to