This is exactly what I am doing - an integration test. I decided to create a separate "test" subproject that is a peer to the "tested" subprojects. I hoped that by declaring the same parent in my test subproject and inheriting all the project's dependencies I will be able to avoid version confusions and test the artifacts whose versions are perfectly aligned. I did not want to employ any hecks to solve my artifact availability problem, but to do it entirely with dependency mechanism available in maven.
Michael McCallum-3 wrote: > > in my particular case i needed the code for integration tests so was > borderline as to whether the artifact was actually separate or not... > > but in general i would agree > On Wed, 14 May 2008 12:02:13 Brian E. Fox wrote: >> If you have classes that you need outside a war, the correct way is to >> make this into a jar that is used externally and also packaged inside >> your war. >> > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Modify-Classpath-tp17215208p17236473.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
