I don't recall ever explicitly running this test myself, but I'm surprised it's causing problems.
Java shouldn't care what OS it's running under. The only thing I can think that might cause this problem is the EOL characters. But Java doesn't care about these, even when the OS does. And SJ should be clever enough not to get tripped up. Could you clarify exactly how you moved your archives? I'd like to see if I can figure out exactly which file is tripping up. Also, do you have a strack trace you can give me? Thanks. --Rob --- David Tam <[EMAIL PROTECTED]> wrote: > I have tried moving archives across operating systems and I was > dissapointed to find out that this doesnt work. > I tried moving from sourcejammer on red hat linux to sourcejammer on > freebsd and I got a corrupt xml message. > I then attempted to move an archive from winXP to freebsd and it also > didnt work. Is there are reason for this? > Can it be done? > > Thanks in advance. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click > _______________________________________________ > SourceJammer-users mailing list > SourceJammer-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sourcejammer-users > Discover Yahoo! Find restaurants, movies, travel and more fun for the weekend. Check it out! http://discover.yahoo.com/weekend.html ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ SourceJammer-users mailing list SourceJammer-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sourcejammer-users
