I see, if you mean a set of profiles, each with a dependencyManagement that makes some things 'provided', then I'm following, and that is what I need.
On Wed, Nov 4, 2009 at 8:32 AM, Jesse Farinacci <[email protected]> wrote: > Benson, > > On Wed, Nov 4, 2009 at 8:22 AM, Benson Margulies <[email protected]> > wrote: >> The problem is that it's not quite 'corporate'. The problem is this: you can >> build a webapp with CXF services that is self-contained on Jetty and tomcat. >> Then, to get it to run on JBoss, you want to start subtracting. OK, well, a >> profile that subtracts. If the profile can just use dependency-management to >> mark these guys 'provided', fine. >> > > Sorry, you've missed the point entirely. I have a top level > corporate-wide "super" POM which mostly just manages a giant > dependencyManagement section. You don't have to be a corporate user to > have something like this in place, all advanced Maven projects I've > ever encountered do this... > > Anyhow, create separate modules like jetty-dependencies, > tomcat-dependencies, jboss-dependencies, which have all the correctly > scoped dependencies in them, perhaps you'd even want to attach some > m-enforcer-p checks to verify stage that nothing has slipped in. Then > use a profile to depend on the proper container-dependencies module. > > As for exclusions, I'm really not sure what kind of things would be > causing problems.. Can you give an example? > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > 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]
