You integration project surely depends on the main project. that is why when ever you make changes in main project you must run jar:install to place its jar into local respository and the integration to pickit up automatically.
Also, when ever you have to multiple projects collabrating together, use maven-multiproject-plugin. For your case root main integration (depending on main) What you mean "hardcoding the jars' location"? It should be picked up automatically by the integration project. -D On Fri, 18 Mar 2005 12:47:37 +0100, Ralph Pöllath <[EMAIL PROTECTED]> wrote: > Thanks Dan. > > I set up a separate project as you suggested, which includes a > dependency on the main project. > > This works fine, but it requires me to jar:install my main project each > time I run the integration tests. > > So I'd like to make the integration tests a subproject and add a > dependency on the parent project's jar. Is that possible without > hardcoding the jar's location? > > Cheers, > -Ralph. > > On 02.03.2005, at 19:02, dan tran wrote: > > Ralph, > > > > I would add another project to house your integration test cases. > > The source of the testcase must stay in the main source directory. > > (not the unit test src) > > > > After that, use jelly/java to drive your integration in maven.xml > > > > -D > > > > On Wed, 2 Mar 2005 17:42:31 +0100, Ralph Pöllath <[EMAIL PROTECTED]> > > wrote: > >> Hi, > >> > >> In addition to my unit tests, I have some integration tests which I'd > >> like to be able to run separately (they require a database to be > >> available, etc). > >> > >> What's the preferred way to do this with maven? > >> > >> Thanks, > >> -Ralph. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
