I've been facing the same issue with apache commons configuration. I've checked its source repository at apache and noticed this component was being generated by maven 1. And that might be the reason its pom at central repository has some many compile dependencies since compile is the default scope in maven 2. I think it's really important to get it fixed at the central repository to avoid excluding unnecessary dependencies every time a sort of packaging is needed. What would be the steps to get it updated at ibiblio ? Whom should I contact ? commons configuration developers or an ibiblio administrator ? Thanks, Dário
Wendy Smoak-3 wrote: > > On 11/9/06, jiangshachina <[EMAIL PROTECTED]> wrote: > >> Undoubtedly, Maven central repository is crucial. >> My question just be why so many unessential artifacts are added to pom? >> May there are "some reasons" I don't know. > > The usual case is that the project in question is not using Maven, so > the developers don't realize what happens when they leave all of their > dependencies in the default (compile) scope. > > If you can identify the pom that's causing the problem, it's usually > possible to work with the developers of that project to correct it for > the next release. > > To correct the problem you're having now, I suggest correcting the > poms in your internal corporate repository. (IMO, proxying the > central repo internally is a good idea for several reasons, including > including gaining control of the artifacts you're using and reducing > traffic at the central repo.) > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Too-many-jars-added-to-lib--tf2558368s177.html#a8077263 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
