SQS project's mercurial repository is now hosted on bitbucket.org.
You can sign up bitbucket account for free and fork SQS repositories and we are looking forward to receiving your "pull request".
SQS Project now start to use Jenkins, which is a continuous integration service. It guarantees fully-tested executable file distribution.
The work flow is like this:
- An SQS developer commits and pushes some change sets to a mercurial repository on bitbucket.org.
- Bitbucket.org service kicks jenkins.sqs2.net to start a build process:
- Jenkins service executes "hg update" to refresh mercurial repository on jenkins.sqs2.net.
- Jenkins service executes "mvn deploy" to build an artifact and scp it to maven repository on dev.sqs2.net.
- Jenkins service stores executable jar files into some specific location.
Now the main mercurial repository has changed from sourceforge.net to bitbucket.org, because the mercurial repository of sourceforge.net dosen't have incoming triggers of hg push.
The new repository locations are describe in http://dev.sqs2.net/projects/sqs/wiki/Mercurial_Repository
scm settings in pom.xml file and redmine project have changed, too.
Shared Questionnaire System Project is now separated into 4 subprojects; sqs-editor, sqs-reader, sqs-translator, sqs-util.
This change has made for ease of commitment to the subproject of someone else...
Current JNLP enabled SQS applications have version incompatibility with JRE 6u19 or later.
To use them, you must uninstall current JRE from your system, reinstall JRE 6u18 and launch SQS apps.