Joerg Hohwiller wrote: > 1. ugly maintainence of the project > 2. a jar for each bridge-implementation > I'd hardly say it is ugly maintenance...
> But for 2. there should be a way to build a jar in the top-level project > that includes all code-output compiled in the sub-projects. > Is that making sense for you or is this already targeted by m2? > Do you see a better solution? This can definitely be done (the ant tasks repackage all the dependencies into one jar). As a commons logging user, I'd definitely prefer to be able to just take the api and the implementation that goes with the loggin impl(s) I intend to use. > > BTW. I have seen this issue for aggregated javadocs in maven1 > discussions a long > time ago. Is that solved in m2? Not yet, but it is filed and will be addressed in the near future. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
