I've updated the richfaces kitchensink-rf and helloworld-rf quickstarts with the changes introduced in the JDF versions of those quickstarts. The next step is to include the RichFaces quickstart repository as a sub-module in the jboss-jdf jboss-as-quickstart repository.
However before we proceed with this, I would like to recommend that you first fork the RichFaces quickstart repository and include that fork in your jboss-as-quickstart repository. This will improve your workflow when you want to commit changes to the repository, and subsequently issue a pull request back to the upstream RichFaces repository.
Without first forking the repository you will have to have commit rights to all sub-module repositories in order to be able to commit changes. This defeats the purpose of having things in separate repositories IMO. Note: you can put these forks in an alternate github organisation (jboss-jdf-forks for instance) if you do not want to pollute your jboss-jdf with too many new repos.
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
I've updated the richfaces kitchensink-rf and helloworld-rf quickstarts with the changes introduced in the JDF versions of those quickstarts. The next step is to include the RichFaces quickstart repository as a sub-module in the jboss-jdf jboss-as-quickstart repository.
However before we proceed with this, I would like to recommend that you first fork the RichFaces quickstart repository and include that fork in your jboss-as-quickstart repository. This will improve your workflow when you want to commit changes to the repository, and subsequently issue a pull request back to the upstream RichFaces repository.
Without first forking the repository you will have to have commit rights to all sub-module repositories in order to be able to commit changes. This defeats the purpose of having things in separate repositories IMO. Note: you can put these forks in an alternate github organisation (jboss-jdf-forks for instance) if you do not want to pollute your jboss-jdf with too many new repos.