|
Thanks, I will try to download it in a day or two. Phil suggested to backup the repository itself on a daily basis, which is a practice I will employ, but I also like having the option of occasionally exporting everything to a non-proprietary format "just in case". Thanks again, I hope to post a more positive note in a few days. Shawn -----Original Message----- From: owner-java400-l@midrange.com [mailto:owner-java400-l@midrange.com]On Behalf Of Joe Pluta Sent: Monday, June 18, 2001 8:24 PM To: JAVA400-L@midrange.com Subject: RE: VAJAVA vs CODE/400 For backup, I regularly export my packages to JAR files containing source, so I suppose I misspoke when I said my Java code never becomes .java files. It does, but compressed inside a JAR file. Back in the bad old days of a 64MB 333MHz Pentium running Win/98, I would see occasional lockups. And if you do manage to lock VAJ up, the repository consistency check can take while. But I've not had one of those, as I said, in quite some time. I have a fairly large machine, an 800MHz PIII with 512MB of RAM, so that may help, as does Windows 2000. However, I often run VAJ, IE5.5, NoteTab Pro, Paintshop Pro, Websphere Studio, CODE/400, Websphere adminclient, Outlook, CA Express, Word and Powerpoint all at the same time (this is a typical environment when I write articles) and about the only thing that ever locks up is IE. Joe > -----Original Message----- > From: owner-java400-l@midrange.com > [mailto:owner-java400-l@midrange.com]On Behalf Of Shawn Church > Sent: Monday, June 18, 2001 7:42 PM > To: JAVA400-L@midrange.com > Subject: RE: VAJAVA vs CODE/400 > > > I am not necessarily "required" to work with an outside version control > system, but out of habit and common practice that comes natural. Do you > ever export your code for purposes of backup, etc.? I seems a > little spooky > to trust all my code to the VAJ repository, but maybe that's just me. > > I have been puzzled as to the poor performance of VAJ I have experienced, > which is why I have tried it on several different occasions in different > environments, and hence is reproducable. I can't quickly blame NT, since > nothing else has been problematic, but you also say you haven't had these > types of problems in "quite some time", implying you may have had these > problems at some time in the past? If everyone else which is using VAJ > successfully is also running 2000, then NT may very well be the issue. > Otherwise, maybe I should try VAJ 3.5 sp2. I can't/don't want to > yet go to > 2000, because of the lack of compatibility with a few applications which > don't yet support 2000 (ie - Iris). My reference to "rare" was not to > application crashes in general, but to the point of requiring a system > reboot since the processes were frozen to an extent I could not end them > individually. > > My development is a mix of OS/400, NT, and Linux, but my primary concern > (over cost) is the viability of the product in general. Since it sounds > like my experiences were unique, I should probably try it again. > > If you could address the question about the Java code safety, I would > appreciate knowing "best practices" for this situation. > > Thanks, > Shawn > +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.