Mark McBride wrote: > This is true, there's actually only a handful of jars that are actually > compiled against. The only concern I have with only entering those > handful of jars as dependencies is that somehow a developer could change > the version of the jdbc driver not knowing that it has really already > been dictated by oc4j's manifest.mf. I'll admit that this is being a > little picky, but I would like to get our configuration exactly the same > as our target deployment environment. This will be easier when we can > group dependencies together so that there's more meaning. But for now > I'm reading that I should probably just enter those dependencies in the > project.xml.
You could write some custom jelly in your project xml that would parse the manifest and compare the versions to those defined in the project descriptor. THis way you can verify that the versions are synchronized easily on each release (or even each build). R. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
