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, > > -- With Regards, Martin Taal Openbravo M: +31 6 288 48 943 @: [email protected] Skype: martintaal Openbravo Headquarters: P: +34 93 27 25 947 F: +34 93 27 25 905 Address: Edificio Slan, Planta 2a, Landaben, Calle J, 31012 Pamplona, Navarra, Spain Mailing address: PO Box 5117, 31010 Pamplona, Navarra, Spain ------------------------------------------------------------------------------ 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
