Hi Rick, I tried to take a "beginner's mind" and explore the Getting Started guide with 10.15.
I stumbled a bit, and I'm wondering if we could do a bit of smoothening and path-straightening prior to release. First of all, I searched and didn't find a simple "one-pager" describing CLASSPATH versus MODULEPATH, why it matters, how I would go about choosing which configuration approach to use, what the restrictions are on switching back-and-forth, etc. Perhaps we could put something like that up at the very beginning, in either "Deployment Options" or "System requirements"? Secondly, is it true that if I use either "java -jar derbyrun.jar" or the scripts in the bin/ directory, then I'm going to be using only CLASSPATH, not MODULEPATH? I couldn't figure out how MODULEPATH would have any interactions with either of those methods. If this is the case, then maybe a sentence at the start of "Choosing a method to run the Derby tools and startup utilities" describing this would help. Lastly, I think this might be just an oversight from some time in the past, but with my "beginner's mind" I was struck by how awkwardly we introduce the NetworkServer in the Getting Started manual. For example "Using the Derby tools and startup utilities" starts out by saying "The tools that are included with Derby are dblook, ij, and sysinfo." Then about in the middle of the page it suddenly dumps "NetworkServerControl" into the mix. And nowhere in the entire Getting Started manual do I find anything at all about the startNetworkServer and stopNetworkServer scripts in the bin/ directory. Instead, the "Activity 4" section just tells you to use "java -jar derbyrun.jar" to start and stop the Network Server, which is awkward as heck if you chose to use the bin/ scripts when you launched into "Getting Started with Derby". Anyway, I realise that nearly all of this pre-dates the modularization work that you did, but I thought it was worth sharing the feedback regardless. Oh, and BTW, all my testing continues to go well, haven't found any actual code problems to note yet. thanks, bryan
