Re: [m2] [evangelism] [suggestion] New libraries coming out
Alexandre Poitras schrieb: Nah only correcting errors. Lot of POMs are invalid right now. Ah ok. So fixing a pom which did not work before... -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] [evangelism] [suggestion] New libraries coming out
Yeah, that's what I meant :) On 12/15/05, Christian Schulte [EMAIL PROTECTED] wrote: Alexandre Poitras schrieb: Nah only correcting errors. Lot of POMs are invalid right now. Ah ok. So fixing a pom which did not work before... -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards, _ Arik Kfir[EMAIL PROTECTED]
Re: [m2] [evangelism] [suggestion] New libraries coming out
Hi, Sorry for butting in - but how about adding some (willing) people as administrators of *parts* of the ibiblio repo? I for example wouldn't mind being responsible for managing, say, the jboss section. This means that the admin only has permissions for that particular directory of the ibiblio repo and he/she need only to concentrate on that (new versions, POM fixes). We can thus divide the workload between the community and let the core Maven team concentrate more on the core product. In addition, if every admin is responsible for a group of products he/she are using anyway, I'm sure the quality of the POMs and their maintenance will go up as well. What do you think? On 12/14/05, Ralph Pöllath [EMAIL PROTECTED] wrote: On 14.12.2005, at 10:14, cameron101 wrote: It would be great if the likes of Spring / Hibernate and other mainstream OSS vendors released new versions to Maven with all the POM's and direct dependencies. They themselves would benefit as the community would probably have a faster take up of new technologies and therefore progress the discovery and fixing of bugs and new functionality. Unfortunately, this sounds highly unlikely for Spring. They just demoed their build system common-build at the Spring Experience conference which is based on Ivy: http://www.jroller.com/page/raible? entry=spring_agile_development_challenges_by So yes, I agree we need more lobbying. I love Spring, but I don't need yet another build system. Cheers, -Ralph. On 13/12/05, Srepfler Srgjan [EMAIL PROTECTED] wrote: I personally think that we should lobby for grater use of maven2. I mean with all respect to maven you team just can't and shouldn't handle this enormous repository. I mean the hibernate guys should build their libs with m2 pom and also house the libs themselves. I mean we can't really bother your people for every little thing like hibernate annotation 3.1beta*7* or something else I mean come on, you have lives too :) Same thing goes for spring libraries, or any other project. - 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]
Re: [m2] [evangelism] [suggestion] New libraries coming out
This is exactly what we plan to do. There is work under way to set up the necessary permission system and web of trust. Ideally, it will be the projects themselves doing so, but we realise this won't always be the case. BTW, we just did a big key signing at ApacheCon. If you ever wind up at a face to face with other people in the community, make sure you create and sign each others PGP keys! Cheers, Brett On 12/14/05, Arik Kfir [EMAIL PROTECTED] wrote: Hi, Sorry for butting in - but how about adding some (willing) people as administrators of *parts* of the ibiblio repo? I for example wouldn't mind being responsible for managing, say, the jboss section. This means that the admin only has permissions for that particular directory of the ibiblio repo and he/she need only to concentrate on that (new versions, POM fixes). We can thus divide the workload between the community and let the core Maven team concentrate more on the core product. In addition, if every admin is responsible for a group of products he/she are using anyway, I'm sure the quality of the POMs and their maintenance will go up as well. What do you think? On 12/14/05, Ralph Pöllath [EMAIL PROTECTED] wrote: On 14.12.2005, at 10:14, cameron101 wrote: It would be great if the likes of Spring / Hibernate and other mainstream OSS vendors released new versions to Maven with all the POM's and direct dependencies. They themselves would benefit as the community would probably have a faster take up of new technologies and therefore progress the discovery and fixing of bugs and new functionality. Unfortunately, this sounds highly unlikely for Spring. They just demoed their build system common-build at the Spring Experience conference which is based on Ivy: http://www.jroller.com/page/raible? entry=spring_agile_development_challenges_by So yes, I agree we need more lobbying. I love Spring, but I don't need yet another build system. Cheers, -Ralph. On 13/12/05, Srepfler Srgjan [EMAIL PROTECTED] wrote: I personally think that we should lobby for grater use of maven2. I mean with all respect to maven you team just can't and shouldn't handle this enormous repository. I mean the hibernate guys should build their libs with m2 pom and also house the libs themselves. I mean we can't really bother your people for every little thing like hibernate annotation 3.1beta*7* or something else I mean come on, you have lives too :) Same thing goes for spring libraries, or any other project. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] [evangelism] [suggestion] New libraries coming out
This sounds great brett - glad to hear that. On 12/14/05, Brett Porter [EMAIL PROTECTED] wrote: This is exactly what we plan to do. There is work under way to set up the necessary permission system and web of trust. Ideally, it will be the projects themselves doing so, but we realise this won't always be the case. BTW, we just did a big key signing at ApacheCon. If you ever wind up at a face to face with other people in the community, make sure you create and sign each others PGP keys! Cheers, Brett On 12/14/05, Arik Kfir [EMAIL PROTECTED] wrote: Hi, Sorry for butting in - but how about adding some (willing) people as administrators of *parts* of the ibiblio repo? I for example wouldn't mind being responsible for managing, say, the jboss section. This means that the admin only has permissions for that particular directory of the ibiblio repo and he/she need only to concentrate on that (new versions, POM fixes). We can thus divide the workload between the community and let the core Maven team concentrate more on the core product. In addition, if every admin is responsible for a group of products he/she are using anyway, I'm sure the quality of the POMs and their maintenance will go up as well. What do you think? On 12/14/05, Ralph Pöllath [EMAIL PROTECTED] wrote: On 14.12.2005, at 10:14, cameron101 wrote: It would be great if the likes of Spring / Hibernate and other mainstream OSS vendors released new versions to Maven with all the POM's and direct dependencies. They themselves would benefit as the community would probably have a faster take up of new technologies and therefore progress the discovery and fixing of bugs and new functionality. Unfortunately, this sounds highly unlikely for Spring. They just demoed their build system common-build at the Spring Experience conference which is based on Ivy: http://www.jroller.com/page/raible? entry=spring_agile_development_challenges_by So yes, I agree we need more lobbying. I love Spring, but I don't need yet another build system. Cheers, -Ralph. On 13/12/05, Srepfler Srgjan [EMAIL PROTECTED] wrote: I personally think that we should lobby for grater use of maven2. I mean with all respect to maven you team just can't and shouldn't handle this enormous repository. I mean the hibernate guys should build their libs with m2 pom and also house the libs themselves. I mean we can't really bother your people for every little thing like hibernate annotation 3.1beta*7* or something else I mean come on, you have lives too :) Same thing goes for spring libraries, or any other project. - 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] - 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]
Re: [m2] [evangelism] [suggestion] New libraries coming out
Brett Porter wrote: This is exactly what we plan to do. There is work under way to set up the necessary permission system and web of trust. Ideally, it will be the projects themselves doing so, but we realise this won't always be the case. BTW, we just did a big key signing at ApacheCon. If you ever wind up at a face to face with other people in the community, make sure you create and sign each others PGP keys! Cheers, Brett Sounds like a great initiative, it'll help us manage the repo, it'll benefit the upstream devs and the downstream devs as well. I believe that if a project comes out that already uses m2 they should be allowed to manage their own repos, what do you think? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] [evangelism] [suggestion] New libraries coming out
Arik Kfir schrieb: Hi, Sorry for butting in - but how about adding some (willing) people as administrators of *parts* of the ibiblio repo? I for example wouldn't mind being responsible for managing, say, the jboss section. This means that the admin only has permissions for that particular directory of the ibiblio repo and he/she need only to concentrate on that (new versions, POM fixes). Hmm...POM fixes !?! Fixing a POM means making a new release, or ? I definitely would not want any deployed artifact to change in the repository once deployed. That would mean having to permanently monitor the repository for changes. -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] [evangelism] [suggestion] New libraries coming out
Nah only correcting errors. Lot of POMs are invalid right now. On 12/14/05, Christian Schulte [EMAIL PROTECTED] wrote: Arik Kfir schrieb: Hi, Sorry for butting in - but how about adding some (willing) people as administrators of *parts* of the ibiblio repo? I for example wouldn't mind being responsible for managing, say, the jboss section. This means that the admin only has permissions for that particular directory of the ibiblio repo and he/she need only to concentrate on that (new versions, POM fixes). Hmm...POM fixes !?! Fixing a POM means making a new release, or ? I definitely would not want any deployed artifact to change in the repository once deployed. That would mean having to permanently monitor the repository for changes. -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
