Hi, I simply think that it is an unnecessary overhead and all controls who are working towards a release have to compile all the time anyways so I don't see the point of having a build foreach of them individually.
The same would be true for all projects at Eclipse - if each bundle would be built seperately this wouldn't work right. I know we are kind of special because every widget owner is responsible for his/her widget but I think creating a build for each widget makes things even more complicated. Doing an all in one build puts more pressure on the developers to keep their repo clean and if they refuse to do so we need to drop their widget from the release builds. Tom Am 19.11.11 02:00, schrieb Wim Jongman: > > > Well the one that breaks the build is responsible for fixing. I really > don't think that it is pratical to have a build job for each widget. > > Why not? > > > > > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev -- B e s t S o l u t i o n . a t EDV Systemhaus GmbH ------------------------------------------------------------------------ tom schindl geschäftsführer/CEO ------------------------------------------------------------------------ eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833 http://www.BestSolution.at phone ++43 512 935834 _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
