Hi all,Hi all, Kenny has offered to help out getting the SOA-P quickstarts into shape - making sure they are consistent with those we have for EAP etc. >From our side, Sande and Rafael can both help you, as can I. The best way to get help is to join #jboss-jdf on freenode. A few resources to start with: * Contribution guide - https://github.com/jboss-jdf/jboss-as-quickstart/blob/master/CONTRIBUTING.md - cover lots of stuff like code formatting * For those with access - overall developer experience requirements - https://docspace.corp.redhat.com/docs/DOC-136011 * QSTools - Rafael, please provide the link - this tool automates many of the checks we do on quickstarts
To verify if your code followed the General Guidelines you can run QS Tools on your project.
To run QS Tools, go to your quickstart project root and execute:
mvn -U org.jboss.maven.plugins:maven-qstools-plugin:check
This
will generate a report on QUICKSTART_HOME/target/site/qschecker.html.
Review the report to determine if your quickstart project
violates any item in the General Guidelines.
In general, one of our big requirements is that there are a lot of comments in the code, this is often the most laborious area, and hopefully one where Kenny can really help, as he knows about the subject :-) The goal here is to get any quickstarts that we have on the SOA-P side ready for inclusion in JDF, and also to identify any gaps we may have, and find volunteers to work on those. It's also worth thinking about an archetype or two for SOA-P at the same time. Rafael's QSTools is able to generate archetypes from quickstarts, so it's really just a case of identifying which quickstart(s) to base it on. Finally, I should mention that do want to focus on SOA-P here, not on the upstream projects. Kev, Keith, could you respond with what you know we have in SOA-P land today, and where Kenny et al can start to take a look? Pete _______________________________________________ jdf-dev mailing list jdf-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev