The simplest thing to do would be to create a working webapp in Maven first, one that has no dependency on the library you want to test. A good way to do this would be with the archetype for webapps.
Once that works, add a <dependency> to your webapp that references the library. That should allow you to write code in your webapp that calls the library. I'm not sure what you mean by "I would like it so that the sub-project has it's own set of dependencies that are not bundled." The webapp doesn't need to be set up as a "sub-project." Give that a try and come back to the list if you run into problems. -----Original Message----- From: Dan Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 11:07 AM To: [email protected] Subject: using a webapp to test a project Hello, I'm a little to maven so forgive me. I'm using maven 2 and I have a library that I would like to test but I would to test it with a web application that runs in jetty. How would something like this work as far as where the files would go and how it would effect the pom? Could the webapp be a sub-project? I would like it so that the sub-project has it's own set of dependencies that are not bundled. Thanks. -- Dan Adams Software Engineer Interactive Factory --------------------------------------------------------------------- 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]
