Hi, >OK, you are right, but I think, is really better to have the same code in >one file -- i think is;t better than have one code in a lot of files, don't >you? :)
I completely agree, but the above is unrelated to your previous question. The same code should only be in one file, of course. Then you're only developing one place. Each time you make a new version of this shared library, you deploy it to all the applications that use it. This is elementary development process engineering. Don't waste your time hacking around strange classpath configurations, you'll get only headaches in the long run. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
