I'm no Maven expert, but I believe we ended up doing it that way because it allowed subprojects to override those dependencies. I think if your subproject specifically needs it, you simply add it as a dependency to your pom and change it to required. You don't have to define a version - that should come from the parent.
The reason to have it in the parent was to standardize the versions, but not define many required dependencies. If you do make any change, please build and test the entire tree to mae sure it doesn't break something else. Jeremy Thomerson http://www.wickettraining.com -- sent from a wireless device -----Original Message----- From: James Carman <[email protected]> Sent: Saturday, March 21, 2009 8:01 AM To: [email protected]; [email protected] Subject: Wicketstuff Core Dependency Management... The dependencies in the main wicketstuff-core are "scoped" for stuff like slf4j and jetty to be "provided". This totally screwed me up when I was trying to write an example application (the log4j stuff wasn't showing up because it was marked as provided by the parent pom). Does anyone care if I remove the scope declarations from the <dependencyManagement> section in the wicketstuff-core parent pom? It fixed my problem when I did. James --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
