[maven-release-plugin] prepare release jangaroo-tools-1.0.1
[maven-release-plugin] prepare for next development iteration
Revert "fixes Joo-19 http://jangaroo.myjetbrains.com/youtrack/issue/JOO-19 When scanning all EXML files, for the created ConfigClass objects, evaluateSuperClass() was not called. This change: Much simpler solution, it seems we can evaluate the super class immediately"

This reverts commit b1eb4382cf2f72631460a92d776ebd498d056a3d.
fixes JOO-63
http://jangaroo.myjetbrains.com/youtrack/issue/JOO-63
super config class not found during EXML compilation

Reverted the "optimization" that caused the new bug :-(

This reverts commit b1eb4382cf2f72631460a92d776ebd498d056a3d.
fixes JOO-62
http://jangaroo.myjetbrains.com/youtrack/issue/JOO-62
joo.loadStyleSheet() only works for 31 style sheets in IE

As a special case for IE, using conditional JScript code, we
record all joo.loadStyleSheet() calls and "flush" every 31
style sheets and at the very end of jangaroo-application.js
by creating a <style> element with an @import directive for
every recorded style sheet.
Note that if not using the Maven build process that generates
jangaroo-application.js and using joo.loadStyleSheet(), you
have to call the new function joo.flushStyleSheets() manually
to make joo.loadStyleSheet() work in IE (even for less than 31
style sheets)!
ignore jangaroo-1 release POM updates
Merge branch 'jangaroo-1'

Conflict was just because of adjacent lines.

Conflicts:
	jangaroo-maven/jangaroo-maven-plugin/src/main/java/net/jangaroo/jooc/mvnplugin/PackageApplicationMojo.java
[maven-release-plugin] prepare release jangaroo-tools-2.0.5
[maven-release-plugin] prepare for next development iteration
Merge commit '128abb4888d89d5a18114ae6c53d34dcbc5edeaa' into jangaroo-3
ignore Jangaroo 2 release
Refactoring [Embed] code generation; revealed bug: new String()
was missing for non-static fields with [Embed] annotation.
make as3! and new! RequireJS plugins work in build mode
restore [Embed]ding images for Jangaroo 3;
makes ChessFlash work like a charm again
represent Error's name and message properties by get/set functions,
so subclasses can override them for documentation purposes
changes to generate Ext 4.2 API:
* make root package configurable
* for compatibility, put all config classes in one config
  package again
* generate more config classes: not only when it has an
  alias, but whenever class has cfgs
* try harder to find super config class (walk up)
* fix singleton name
correct ASDoc in joo-api stubs:
* replace windows line endings in ASDoc strings (\r\n) by simple \n
* to avoid double asterisk (" *  * ") in generated APIs, remove pattern
  /\s*\* ?/ from beginning of ASDoc lines
After some more changes and fixes, ExtAsApiGenerator quite successfully
generates an ActionScript API for a jsduck JSON export of Ext 4.2.0.
* made AMD name of JS framework configurable (parameter 4)
* add configs from mixins to config classes
* add ASDoc of target class to corresponding config class
* if there are multiple aliases (xtypes), chose the one that most closely
  resembles the Ext 3.4 AS API
* for the time being, do not convert get/set methods into get/set properties
get rid of Maven warning by removing duplicate dependency