I'm not sure if there's a way to do this ... I'm hoping there is. I'd like to be able to have a dependency be for the compilation only, without being included in the installation. I'm worried about my WARs specifically. They have a dependency on an EJB project, which of course has a dependency on a J2EE JAR from a local repository. However, since the J2EE classes are going to be supplied by JBoss, I don't really want them to be included in the WAR when they get built and installed.
Any ideas? It looks like a scope of "compile" still includes it in the WAR, while a scope of "runtime" won't allow the ejb project to be built at all. As always, thanks for the help! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
