Hi, Maybe I couldn't express my point in a good manner, English is not my mother tongue.
My point is similar to Juan Pablo's if we want to check in compiled jar files to the repository, we need to handle them like that, "Third-party" libraries that should have their own repository, and then with a property svn:external we link the .jar on the lib folder. For me having the jar file and the source code of a 'external' library in the same repository of Openbravo's source code, is a little bit odd. But this is just my opinion. I don't know if there is a way to declare a external link, like svn:external in Mercurial, maybe Juan Pablo can explain. Just my five cents. Best Regards, -- Iván Perdomo On Fri, 30 Jan 2009 20:49:23 +0100 Martin Taal <[email protected]> wrote: > Hi, > To react on the previous posts: > > - This effort of checking in the three jar files is part of an effort > to create a build.quick task which if nothing changed takes very > little time. Little time means that we should be very critical on > which tasks actually need to be run multiple times a day by each one > of us (even if they take 6 seconds total). > > - Ant tasks should not depend anymore on wad.lib, trl.lib, core.lib > or call these targets. This means that the core, wad, trl jars are > not modified in day-to-day work. No need to add to svn:ignore or > other workarounds. > > - Afaics it is not that much of an issue to have the jar file in the > repository. If you change the something in core, trl, wad then it is > just running the wad.lib, etc. task (same as now) and commit the > changed library. What mess would this create? > Also for me it is far more visible (in Eclipse Team Synchronization) > to see that a core, wad, trl jar file has changed then checking if > something changed in one of the three other projects. > > gr. Martin > > Iván Perdomo wrote: > > Hi, > > > > I'm one of the *few* developers that have modified the core, trl and > > wad (some times), and I don't like the idea of having the jar files > > in the repository. > > > > Having to check in the source modification and the new jar files > > will be a mess, and, as Juan Pablo stated, the process of checking > > in this changes will be odd. > > > > Cheers, > > > > > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
