This other was not overwritten http://jira.codehaus.org/browse/MEV-58
It'd be interesting to know if the sync will override it always or only when there're changes to the same file in the apache repo. I would suggest also to turn off the syncing of poms that already exist in the destination because this is causing a bottleneck, sometimes I can't fix the poms at the source repo because I don't have rights. Anyway I'm not sure if it's "ethic" to change the files without notifing the projects involved and I'm not ready to subscribe to hundreds of mailing lists. We definitively should make a responsible in each sync'ed repo subscribe to a mailing list so we can get in touch with each project through him. Regards. On 8/30/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Is it also being fixed at Apache? Remember that it will be overwritten > next sync otherwise... > > It is also worthwhile modifying the commons build files so that future > releases are ok. I can apply patches. > > - Brett > > Carlos Sanchez (JIRA) wrote: > > > [ http://jira.codehaus.org/browse/MEV-73?page=comments#action_45529 ] > > > >Carlos Sanchez commented on MEV-73: > >----------------------------------- > > > >Fixed in ibiblio > > > > > > > >>commons-collections is missing scope > >>------------------------------------ > >> > >> Key: MEV-73 > >> URL: http://jira.codehaus.org/browse/MEV-73 > >> Project: Maven Evangelism > >> Type: Bug > >> Components: Invalid POM > >> Reporter: Carsten Ziegeler > >> > >> > > > > > > > >>The dependency for junit needs the scope test > >> > >> > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
