Package Torello.Java.Build

Useful Project Building Classes for Building a Suite of Tools into a '.jar' File and a Documentation Website. Currently requires working with Google Cloud Platform.

These classes form the core of the build routine for this JAR Library.

BTW, this ENTIRE THING is really just a collection of thousands of little field-settings, decision-predicate's and indirection-references. If that also doesn't make any sense - the only purpose of the 'Build' package is so that I don't have to type over-and-over-and-over (and over) hundreds of little "Make-File" instructions at the Command-Line whenever I want to compile a package and put the updated 'javadoc' on my web-page!.

Literally, 'BUILD' is the only way anything in this project ever gets done. What this package does do very well is that it makes most things that I do when writing code for this JAR-Library a single line command-invocation at the command-line. I mean, that's the whole thing.

At this stage, it is (sort of) the most important package in this project. However, by the same token, given the level of documentation and explanatin that would be needed to make this usable and accessible for others - it isn't exactly finished yet. Specifically, I don't expect others to starting writing projects that use this for their build (not yet, anyway). When it is finished, it will be very easy to write as many packages as you would like and compile them, document them, and upload them to your cloud storage buckets very easily.

When I am working, two of the dozens of screens that I am looking at thanks to all the work that has gone into the 'Build' part of this Java JAR-Library are screen captured below:





Seriously, this whole package "feels like" one GIANT if-then-else statement with millions of micro-configurations. As a '.jar'-File grows in size, the number of combinations, configurations and settings that are used increases. During your coding sessions, being able to type a single command and see the files you want compiled, documented, and pushed out to your Documentation and Distribution Web-Site needs to be easy.

All this package does is help save you typing. There is no way to type all of the javac, move, copy, delete, make-public commands with your fingers when you are trying to debug a new class or interface or method in your project. Build does the "repetitive typing" for you. It is just one giant if-then-else statement that can compile, javadoc, tar & jar, and then move copy and delete things.

In its current incarnation, it just isn't documented enough for anybody but me to be able to use it. Soon, after JavaDoc.Upgrade is working, I will thoroughly explain this. The nice thing it does, is turn a project into a '.jar'-File and a Java-Doc Web-Site. That is of tremendous benefit if you are worried about your A.P.I.

Supporting Infrastructure:
The classes in this Package may, at first glance, be deceptively simple. Quite a bit of effort was put into the classes in package Torello.Java. The work-horse behind these classes include: