Thanks for trying Roo and sharing your experiences. Sorry you didn't get up an app running in the 10 minutes. Hopefully the following will offer some reasons why...
Regarding issue tracking, if you look at the Roo home page (http://www.springsource.org/roo
) it contains a link caled "Full Project Resources Index". If you click that, it contains a link to the "Jira issue tracker" at http://jira.springframework.org/browse/ROO
. We are working on a new home page at present and will make this easier in the future. In the meantime we've got almost 700 bugs in there, so I guess plenty of people have found it. :-)
In relation to the javax/xml/bind/JAXBException, this is actually a bug in Hibernate Validator on Java 5. If you check the "known issues" section of the Roo reference guide we cover this. It's not Roo's fault at all. Here's the link to our docs which explain: http://static.springsource.org/sprin...e-known-issues
Concerning the repository setup, we use the SpringSource Enterprise Bundle Repository as Roo 1.0.x applications aim to provide an OSGi-compatible experience out of the box. The reasons for the different artefact names is detailed in the FAQ question at http://www.springsource.com/repository/app/faq#q13
. You may be pleased to know we're evaluating switching to Maven Central repositories for Roo 1.1.0, as we agree this can cause confusion. The time spent setting up Nexus, though, to be fair, is not due to Roo but due to your company's firewall/repository policies/preferences.
You're always welcome to ask us questions at the Roo forum at http://forum.springsource.org/forumdisplay.php?f=67
. We're very friendly and keen to help.
Project Lead, Spring Roo
SpringSource - a division of VMware