WSAD > Server Configuration > Paths > Class Path > Add External JARs

I don't recommend using "Add External JARs" because it may cause classloader issues down the road.  It can also conflict with the server's jar files.

Better, and more standard approach:

For WAS 4.x, pub your jars in <appserver home>/lib/app directory.  Do the same in your WSAD environment.  The path is a little different:  <WSAD home>plugins\com.ibm.etools.websphere.runtime\lib\app.

Then in your web and EJB projects, right click the project, do "java build path", then on the "libraries" tab, click "add variable".  There will be a variable like WAS_PLUGINDIR (depends on version) ... pick that and click extend to add /lib/app/jarname.jar to the path.

You don't have to change the runtime classpath cuz it's automatically picked up.

For WAS 5.x and 6.x, you have to add a shared library on the server.  The /lib/app is no longer supported there.  Go to AdminConsole, expand "Environment" node, then click on "shared libraries".  Point to a path for your jars.  Actually it can be any path, but since it's a shared library it can be pointed to from any of your apps AND you can change the location of the jars just by changing the ONE shared library entry.  In WTE (in WSAD), the easiest way to do the same thing is open your server config, check "enable admin console" on the second tab, save and restart your server, then right click on your server node and choose "run admin console".  This will give you the exact same console as used for the full WAS.  Do everything the same way.

Finally, for 5.x and 6.x, in you WSAD project follow the same instructions as for WSAD 4 above.

HTH!

but then the whole point of putting the shared libraries in CVS goes away ...?

I mean this sounds so much more hectic ...

The best option would be to create a project to store all of the utility jars and then associate the other projects to it so it is a common repository for the utilitys.