On Thu, 2008-06-05 at 15:32 -0500, Wayne Fay wrote: > I haven't used it yet myself, but from my reading of the > documentation, I believe it really only brings in the > dependencyManagement section of the imported pom. So you will still > need to declare struts-core in the project you need to use it, but you > can leave off the version (and scope). > > The real use case for import scope IMO is where a company does not > want to use a single shared corporate parent pom, but they do want to > enforce versions on all projects. So you manage versions in the > imported pom (one place), force all your projects to import it (can be > any pom in the repo), and poof they all get version maintenance for > free.
Except that it doesn't "force" lib versions at all. It just provides defaults for when a pom doesn't explicitly set them itself. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
