Generating the Eclipse project for the QueryFunction class

The Component SDK includes a script to generate the Eclipse project for the QueryFunction class.

To generate the Eclipse project for a new QueryFunction class:

From the command line, change to the components/endeca-extensions subdirectory of the Component SDK.
To create a QueryFilter class, run the appropriate .sh or .bat version of the create-queryfilter command.
For example on Linux:
```
./create-queryfilter.sh <queryFilterName>
```
Where <queryFilterName> is the name you want to use for the QueryConfig class. The name cannot have spaces.
The command creates a new directory called <queryFilterName>-QueryFilter in the endeca-extensions directory.

This directory is an Eclipse project that you can import directly into Eclipse.

It contains an empty sample implementation of a QueryFilter.
To create a QueryConfig class, run the appropriate .sh or .bat version of the create-queryconfig command.
For example on Linux:
```
./create-queryconfig.sh <queryConfigName>
```
Where <queryConfigName> is the name you want to use for the QueryConfig class. The name cannot have spaces.
The command creates a new directory called <queryConfigName>-QueryConfig in the endeca-extensions directory.

This directory is an Eclipse project that you can import directly into Eclipse.

It contains an empty sample implementation of a QueryConfig.

For both QueryFilter and QueryConfig classes, the skeleton implementation:

Extends either QueryFilter or QueryConfig.
Creates stubs for the applyToDiscoveryServiceQuery, toString, and beforeQueryStateAdd methods.
applyToDiscoveryServiceQuery and toString are required methods that you must implement.

beforeQueryStateAdd is an optional method to verify the query state before the function is added. This method is used to prevent invalid query states such as duplicate refinements.
Creates a no-argument, protected, empty constructor. The protected access modifier is optional, but recommended.
Creates a private member variable for logging.