On Friday 08 December 2006 03:07, Aaron Siri wrote: > I get the > impression here that some people think that maven is a form of voodoo and > you never know what it is doing or that it can't be trusted. I always know > exactly what is going to be pulled and know when I should short-circuit the > dependency tree.
> Why should *you* dictate what *I* can and can't trust? (because you and I don't know better ;o) ) How many POMs are "correct" (from an OSGi point of view) in the OSS landscape, do you think? How many are "correct" from any point of view? Examples; Jars needed during testing only (ant, junit et al). Jars that are provided by the "host" (servlet, jta, jca) IMHO, there should be no magic bundle plugin at all. A reporting utility so I can construct the manifest and bundle correctly is the first thing, and a validator that somehow warns me when I have made changes to the references and the Manifest may need an update, would be cool. Why not get your hands dirty and create your own plugin? Or, help Jason van Zyl to make the Jar plugin OSGi friendly. He also is fairly clueless of what is needed and best practices, so he should be easy to influence in your direction. Or, use the old plugin if you find that one better. I didn't like that one either, but instead making fuzz over it I forked it and made my own changes that I felt would help me. (see https://scm.ops4j.org/repos/ops4j/projects/pax/maven/osgi-bundle ) I am sure there are others out there. Cheers Niclas
