[ https://issues.jboss.org/browse/FORGE-1261?page=com.atlassian.jira.plugin... ] Thomas Maslen commented on FORGE-1261: -------------------------------------- OK, I tried it (a fresh install of Forge 1.4.1) on another machine that had never been touched by Forge before and yes, you're right, in that environment I couldn't reproduce the problem and Forge works fine. Also, on the original machine, I erased the .forge directory (actually just renamed it to detain it for further questioning) and yes, with that out of the way again Forge works fine. I looked at the contents of the previous .forge directory. Offhand the .forge/config and .forge/config.xml files look pretty innocent. What _is_ interesting (I'm guessing) is that the plugins directory contains one plugin, hibernate-tools-plugin, and (for whatever it's worth) that plugin includes JAR files for both freemarker (an older version, freemarker-2.3.8.jar) and log4j. If necessary I can tar up the old .forge directory and attach it (if this system supports attachments -- either I'm not seeing straight or they are well hidden), but my guess is that the plugins/installed.xml file (cut and pasted below) tells the important part of the tale: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <installed> <plugin api-version="1.0.5.Final" name="org.jboss.hibernate.forge.hibernate-tools-plugin" slot="1.2.0-SNAPSHOT-4f729e5d-125b-46a3-9f07-4ca220ae19c0"/> </installed> I can't say for sure how that plugin got there (I can't even swear that it's the guilty party, but it seems like a plausible candidate), but I'm assuming that it's because I was using JBoss Tools 4.1.0 (in Eclipse 4.3.1) and its embedded Forge 1.3.3. In the new .forge directory there are no plugins (there isn't even a plugins subdirectory yet), even though I have run "new-project", "persistence setup", "entity", "rest setup" and "rest endpoint-from-entity", so I'm guessing that plugin only gets installed if you exercise some of the Forge Eclipse tooling in JBoss Tools? (And perhaps this version of the plugin was installed by Forge 1.3.3, whereas perhaps Forge 1.4.1 might install a newer version that might not trigger this problem?). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira