Copied the developer connection info in pom.xml from the root project to this one. There was incorrect reporting of this information by default

Updated the pom.xml file to use the correct group name, point to the correct servers, and include the dependencies repo. Mantis: Fixes #2 Fixes #3 Fixes #4

Fixed pom.xml to point to the new repo server locations. Also added the dependency repo so it can pull in freehep.

* remove unneeded "this."
* shorten code

* use (Key|Window)Adapter instead of Key(Key|Window)Listener when only
  implementing one method
* fix comments

The 3D canvas was not added to the JFrame.

* use tabs instead of spaces for indentation
* remove trailing spaces

Updated .gitattributes and .gitignore to provide better support for enforcing LF eol and preventing binaries from entering the repository

* com.syncleus.test.dann -> com.syncleus.dann
* remove no longer required includes

* sources and resources were only moved, not changed
* moved test sources into separate dir
* adjusted ant build script (targets tested)
* added Maven project file (projects/java_dann_examples/pom.xml)
* added Maven parent project file (projects/dann/pom.xml)
* moved some stuff into parent project, to reduce duplication
* added all-projects maven file for convenience (projects/pom.xml)
* added maven build dirs to gitignore
* renamed dann to dann-core (maven artifactId)

To build all of dann (core + examples), use either of:
* projects/dann/pom.xml
* projects/pom.xml

To build only core, use:
* projects/java_dann/pom.xml

It is NOT possible to build the examples directly with:
* projects/java_dann_examples/pom.xml
Except you have the required version of dann-core deployed
into your (local) maven repo with:

	cd projects/java_dann/
	mvn install

fixes ticket:141 more thoroughly by throwing a ComponentUnavailableException which is included in this commit.  ComponentUnavailableException is intended to be a start towards a self-configuring, self-repairing framework that is aware of missing components or configuration - OR at the very least, can inform the human operator how to fix the situation.  it might also be called FeatureUnavailableComponent ... worth considering.