On 6/12/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
I'm trying to reduce redundancy by removing the javax.servlet:servlet-apiand javax.servlet:jsp-api dependencies inside the subordinate modules, since they are declared in shale-parent ... but that causes compile errors indicating that no API classes are getting added to the classpath. Shouldn't the subordinate POMs be inheriting this dependency from shale-parent?
No. Dependencies come transitively from artifacts, they are not inherited from poms. In this case, servlet-api and jsp-api are marked 'provided' so they are not transitive. The <dependencyManagement> section in the parent pom doesn't take effect until you actually add one of those dependencies to a child pom. It exists to control dependency versions in a single place, so that you only need to specify the groupId and artifactId in the child pom. The net effect here is that you need to leave the javax.servlet:servlet-api and javax.servlet:jsp-api in each pom that needs it. You'll probably want to read about this on the Maven website, something tells me I'm not explaining it very well. :/ -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
