We looked for 1) some time ago without success. IMO it makes no sense to invest relevant time on this for 2.40.
I would not do any change in 2.40 env. just keep it as it is. What is the problem in just removing both libraries and modifying the build process in 2.50 repo while keeping 2.40 as it is? Ismael -----Mensaje original----- De: Juan Pablo Aroztegi [mailto:[email protected]] Enviado el: lunes, 07 de diciembre de 2009 18:02 Para: [email protected] Asunto: Re: [Openbravo-development] Removing stax-api and wstx-asl > 2.35 had end of maintenance a week ago so no longer an issue.. but the > 2.40 case still prevails. Yes, important point. I missed it when thinking about the 2.50 problem. There could be different possibilities: 1) Find a way to make 2.40 use the jars stored in src-db/database/lib. 2) Force developers to copy/remove the files whenever they change from 2.40 to 2.50 or vice versa. And put a check in 2.40's build.xml that fails to export in these jars are not found. We'll agree that 1) is preferable. Juan Pablo ---------------------------------------------------------------------------- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
