Jangaroo 2: new build process
Since Servlet 3.0 allows to put Web resources into a JAR under META-INF/resources, we
 no longer need a special (un)packaging for JavaScript files.
 State: compiles and tests are green (some EXML tests disabled that access ext-as as a
 forward dependency!), save unit test mode (you have to skipTests in Jangaroo projects).
new version 2.0.0-SNAPSHOT here on jangaroo-2 branch
simplified jangaroo-2 build process:
* dependencies are no longer of a special type "jangaroo", but simply "jar"
* no longer collect + unpack "jangaroo" jars
* "war-package" only generates jangaroo-application.js, now in target/jangaroo-output
* look into META-INF/resources to find joo/<artifactId>.module.js
Merge branch 'master' into jangaroo-2

Conflicts:
	exml/exml-converter/pom.xml
Merge branch 'master' into jangaroo-2
some more fixes for new Maven resource locations
and Jangaroo test Jetty setup
Merge branch 'master' into jangaroo-2
missing version update after integrate from master
Only write "// FROM ..." message if the module actually contains a *.module.js or
*.classes.js file
Merge branch 'master' into jangaroo-2
Merge branch 'master' into jangaroo-2
Merge branch 'master' into jangaroo-2
Merge branch 'master' into jangaroo-2
changing version schema for Jangaroo 2:
using 2.0-preview-n instead of 2.0.n to indicate that
the upcoming releases will not yet be "final".
The only code where this matters is when the Runtime
compares version numbers. We resolve "-preview-" to
negative numbers starting at int.MIN_VALUE, so we have
lots of tries before the final... ;-)
Merge branch 'master' into jangaroo-2
creating a custom *-sources.jar had negative effect: since we now use normal
jar packaging, during the release, another *-sources.jar is created by the
maven-source-plugin. This jar was signed, but then overwritten by our custom
jar (or the other way round), resulting in a non-matching signature <8*)
The solution is to simply replace our custom source jar creation by
configuring the additional source path and let the standard maven-source-plugin
perform its task.
[maven-release-plugin] prepare release jangaroo-tools-2.0-preview-1
[maven-release-plugin] prepare for next development iteration
Merge branch 'master' into jangaroo-2

Conflicts:
	jangaroo-maven/jangaroo-maven-plugin/src/main/java/net/jangaroo/jooc/mvnplugin/PackageApplicationMojo.java
also ignore .idea directory