> I get confused by the scope thing.If scope is test > , does that mean > the jars will only be used in the test phase of the > build lifecycle?
Exactly, they are only available for the phases needed for the test compile, executing the test and building the test reports. This are the following phases of the default lifecycle (more at http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html ) .) generate-test-sources .) process-test-sources .) generate-test-resources .) process-test-resources .) test-compile .) test and for what i know also the integration test phases: .) pre-integration-test .) integration-test .) post-integration-test plus the phases from the site lifecycle (for building test reports) lg, strub --- Jeff Mutonho <[EMAIL PROTECTED]> schrieb: > On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > Scope test is not included in build classpath. > Both "problem" jars are > > scoped "test". The others have no scope so they > default to "compile". > > > > Wayne > > > > I get confused by the scope thing.If scope is test > , does that mean > the jars will only be used in the test phase of the > build lifecycle? > > Jeff Mutonho > Cape Town > South Africa > > GoogleTalk : ejbengine > Skype : ejbengine > Registered Linux user number 366042 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
