Heiko Rupp created JDF-164: ------------------------------ Summary: forge startup fails as repository info is missing Key: JDF-164 URL: https://issues.jboss.org/browse/JDF-164 Project: JBoss Developer Framework Issue Type: Bug Reporter: Heiko Rupp On a fresh checkout of jdf with forge 1.1.2, forge fails with errors http://pastebin.com/q5knCq3e when running it in ticket-monster/demo. Also running "run admin_layer.fsh" inside forge fails. Editing demo/pom.xml and adding repositories a la <repositories> <repository> <id>jboss-public-repo-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> <!-- Explicitly disable snapshots, so Maven won't try to check for updates for snapshot internal (rhq-*) deps. --> <snapshots> <enabled>false</enabled> </snapshots> </repository> <pluginRepositories> <pluginRepository> <id>jboss-public-repo-group</id> <name>JBoss Public Repository Group</name> <url>http://repository.jboss.org/nexus/content/groups/public/</url> </pluginRepository> <pluginRepository> <id>jboss-central-mirror-repo-group</id> <name>JBoss Public Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/developer/</u... </pluginRepository> </pluginRepositories> makes the forge startup quiet without errors. And also allows to "run admin_layer.fsh" Resetting pom.xml to the version from git after this has once run still allows forge to run, so it looks like forge is missing some maven plugins / dependencies that it can not obtain from central. -- 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