Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 4.0.0.Beta1
-
Fix Version/s: 4.0.0.CR1
-
Component/s: project-examples
-
Labels:None
-
Steps to Reproduce:
-
Git Pull Request:
-
Similar Issues:
Description
After importing Kitchensink example from section "JBoss Developer Framework Quickstarts" in JBoss Central, user is prompted to
Show '/jboss-as-kitchensink/.cheatsheet.xml' for further instructions
|
but /jboss-as-kitchensink/.cheatsheet.xml does not exist.
Imported quickstart is named "kitchensink" instead of jboss-as-kitchensink and it has README.md instead of .cheatsheet.xml
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
I just noticed, that this issue also concerns JBDS. Could you, please, fix this also in xml file for JBDS?
Thanks
Radim Hopp
added a comment - I just noticed, that this issue also concerns JBDS. Could you, please, fix this also in xml file for JBDS?
Thanks I have adapted the kitchensink quickstart and added it to the jdf quickstart project - https://github.com/jboss-jdf/jboss-as-quickstart/pull/363
Snjezana Peco
added a comment - I have adapted the kitchensink quickstart and added it to the jdf quickstart project - https://github.com/jboss-jdf/jboss-as-quickstart/pull/363 Applied in master
Fred Bricon
added a comment - Applied in master verified in JBDS 6.0.0.CR1-v20121204-0201-B166
Rastislav Wagner
added a comment - verified in JBDS 6.0.0.CR1-v20121204-0201-B166 I have updated the PR. Now, it uses the commands introduced by https://issues.jboss.org/browse/JBIDE-14333
This cheatsheet will work with a project example based on an archetype if you copy a project to the workspace and import it or rename the project.
The following are the main changes:
1) At the beginning of the cheatsheet, you will see the following command:
<command
required="true"
returns="currentProject"
serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet"/>
The command is obliged because it sets the currentProject variable.
After that, the currentProject variable is used instead of the hard-coded project name.
For instance:
<command
required="true" serialization="org.jboss.tools.project.examples.cheatsheet.openFileInEditor(path=/$
or
<action
pluginId="org.jboss.tools.project.examples.cheatsheet"
class="org.jboss.tools.project.examples.cheatsheet.actions.RunOnServer"
param1="${currentProject}
"/>
Within the action, it is possible to use a variable like
param1="$
{currentProject}"but is not possible to use a variable as
paramN="/${currentProject}
/src/main/webapp/WEB-INF/templates/default.xhtml"
The currentProject variable in the paramN attribute won't be translated which means the openFileInEditor command must be used instead of the org.jboss.tools.project.examples.cheatsheet.actions.OpenFileInEditor action.
We also need to add the runOnServer and launchJUnitTest command.
Snjezana Peco
added a comment - I have updated the PR. Now, it uses the commands introduced by https://issues.jboss.org/browse/JBIDE-14333
This cheatsheet will work with a project example based on an archetype if you copy a project to the workspace and import it or rename the project.
The following are the main changes:
1) At the beginning of the cheatsheet, you will see the following command:
<command
required="true"
returns="currentProject"
serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet"/>
The command is obliged because it sets the currentProject variable.
After that, the currentProject variable is used instead of the hard-coded project name.
For instance:
<command
required="true" serialization="org.jboss.tools.project.examples.cheatsheet.openFileInEditor(path=/$
{currentProject}/src/main/webapp/WEB-INF/templates/default.xhtml,fromLine=22,toLine=26
or
<action
pluginId="org.jboss.tools.project.examples.cheatsheet"
class="org.jboss.tools.project.examples.cheatsheet.actions.RunOnServer"
param1="${currentProject}
"/>
Within the action, it is possible to use a variable like
param1="$
{currentProject}"
but is not possible to use a variable as
paramN="/${currentProject}
/src/main/webapp/WEB-INF/templates/default.xhtml"
The currentProject variable in the paramN attribute won't be translated which means the openFileInEditor command must be used instead of the org.jboss.tools.project.examples.cheatsheet.actions.OpenFileInEditor action.
We also need to add the runOnServer and launchJUnitTest command.
Fixed by https://github.com/jbosstools/jbosstools-download.jboss.org/pull/4