[ https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14333: --------------------------------------------- About cheatsheet variables: I looked around and it seems these are evaluated from the return values of commands. Thus it seems you can do this without introducing a new syntax. In the cheatsheet have: <command result="currentProject" serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet()"/> Now you can refer to currentProject in commands AND the content (which is rather brilliant) as ${currentProject} No need to do this custom {project} replacement - we just need a command that will return the project for the cheatsheet. Then content authors can even have conditionals on this variable wether it is found or not. About "profile" and the commands: Please point me to the javadoc/API for these - i.e. where is the code for these. The commands should have meaningful names. launchJUnit is *not* expected to mess with users profiles or arquillian enablement. And as Fred asks, please provide an example cheatsheet that uses these commands. -- 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