Alright. I'm not really sure what happened, but I've gone ahead and fixed this again. Somehow the sun.jdk module was not being exported to the proper dependencies.

If everyone could please retest and advise if the issue persists, or is resolved, that would be of great assistance.

Looking for verification on java 6 and 7:
So if you run on any of these operating systems. Please post your results here!

Once you have built and installed the latest code from master, you can run the following forge script from your system command line to verify functionality (you should not see any WARNING: The encoding UTF-8 is not supported by the Java runtime.)

$ forge -e "run-url https://raw.github.com/jbossas/quickstart/master/forge-from-scratch/generate.fsh"

Thanks guys!
~Lincoln

On Wed, Apr 25, 2012 at 6:10 PM, Thomas Frühbeck <fruehbeck@aon.at> wrote:
perhaps it helps: the ModuleClassLoader is requested to load this by getResourceAsStream.
At this time the paths known to the ClassLoader seem to be:

"[,
META-INF/maven/org.jboss.forge,
org/jboss/forge/spec/javaee/cdi,
org/jboss/forge/web,
org/jboss/forge/spec/javaee/ejb,
META-INF/maven/org.jboss.forge/forge-javaee-impl,
org,
org/jboss/forge/spec/javaee/jsf,
org/jboss/forge/spec/javaee/validation/completer,
org/jboss/forge/spec/javaee/soap,
org/jboss/forge/spec/javaee,
org/jboss/forge/spec/javaee/validation/util,
org/jboss/forge/spec/javaee/servlet,
META-INF/maven,
org/jboss,
org/jboss/forge/spec,
org/jboss/forge/spec/javaee/jpa,
org/jboss/forge/spec/javaee/rest,
META-INF,
org/jboss/forge/spec/javaee/jpa/provider,
org/jboss/forge/spec/javaee/jpa/api,
org/jboss/forge,
org/jboss/forge/spec/javaee/jta,
org/jboss/forge/spec/javaee/jms,
org/jboss/forge/spec/javaee/validation/provider,
META-INF/services,
org/jboss/forge/spec/javaee/jstl,
org/jboss/forge/spec/javaee/validation,
org/jboss/forge/rest,
org/jboss/forge/spec/javaee/jpa/container]"

not one sun.com ???



--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."