Re: AW: POM inheritance...
"Sasvata (Shash) Chatterjee" <[email protected]>
| Newsgroups | gmane.comp.java.keel.devel |
|---|---|
| Message-ID | <[email protected]> |
Aleks, >I was just wondering if all the dependencies in the project.xml are necessary... I had the impression that in some keel modules there are more dependencies than actually needed (didn't verify it!). > If you sync to latest CVS I think you'll see that the dependencies are far reduced now, thanks to our ability to depend on keel:maven for the final assembly of the project. I'm sure we could cut down even further with more experimentation, and Mike and I have discussed rearranging some classes between keel-core/keel-common/keel-container, such that we can even drop the keel-container dependency from most service/app project.xml(s). A couple of services (svc-authorization-*) depend on Fortress's ProxyObjectFactory to get at the component name, and end up depending on Fortress/Instrumentation. But other than that, the vast majority o modules only depend on Avalon Framework, keel-common, keel-core (and maybe keel-container). I think the example project.xml for "default" got checked in with the version after doing a "keel:maven", and so had the "full" dependency list. I checked in a version recently that is pre-"keel:maven", so it should be much smaller now. Shash http://keelframework.org/documentation.shtml Keelgroup mailing list [email protected] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com