Juan Pablo Aroztegi wrote:
> When we supported JDK 1.5 DBSourceManager required stax-api-1.0.1.jar
> and wstx-asl-3.0.2.jar to export the database correctly. Now that using
> 1.6 is a must, these libraries are not useful at all. The only
> difference they "add" is that they use simple quotes instead of double
> quotes in the XML headers. But they're only used in sourcedata.
> 
> Taking into account that we already use double quotes in
> src-db/database/model, there's no reason to use it differently in
> src-db/database/sourcedata.
> 
> Eliminating this dependency simplifies the development environment setup
> process because there's no need to copy the jar files to $ANT_HOME/lib.
> Plus we'd have 2 jar files less in src-db/database/lib.
> 
> We could say that the risk is close to zero, we'll just change the
> quotes in the sourcedata XML files. So what do you think if we change
> this?

Hi,
i like the idea of simplifying this very much but would like to check 
some more areas:

- sourcedata in modules
- masterdata
- sampledata (big bazaar)

- import client/export client
   but probably ok as import will work with both types of quotes i assume


In addition there could be the following issue:
Not copying the files and changing the persistent xml data in scm is 
enough for new installs.

But old installation still have the files around so produce the 
old-style quotes which doesn't match the new-style quotes in the scm xml 
files.

So people would need to remove the two files to not get change on export..
But i think documenting this could be enough as we made a similar change 
  lately for windows (switching all line-ending chars to linux-style 
line endings).

Stefan

------------------------------------------------------------------------------
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

Reply via email to