Bug 982330 - Modify kitchensink-cordova quickstart subdirectories to use full quickstart name
Summary: Modify kitchensink-cordova quickstart subdirectories to use full quickstart name
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Quickstarts
Version: TBD EAP 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: sgilda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-08 17:26 UTC by sgilda
Modified: 2013-08-12 13:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-12 13:05:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description sgilda 2013-07-08 17:26:32 UTC 
Description of problem:

The kitchensink-cordova quickstart contains ios and android subdirectories below the top level folder for quickstart examples. Each subdirectory has a README for that quickstart. We need to move the information to the top-level kichensink-cordova quickstart and remove the lower level versions. 

We may also want to modify the access URL.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 sgilda 2013-07-08 20:53:06 UTC 
Fixed and merged.
Comment 2 Rostislav Svoboda 2013-07-11 10:20:23 UTC 
kitchensink-cordova is not part of EAP quickstarts zip - at least in EAP 6.1.1 ER2. Is it planned for ER3 to include this quickstart?

If yes, than please follow proper BZ steps and do not put it directly to ON_QA. 
Paul Gier moves all BZs in MODIFIED or POST state to ON_QA when fixes/changes are included in release he is providing to QA. Please coordinate with him.

Target milestone and target release must be set when BZ is in ON_QA.
Comment 3 sgilda 2013-08-12 13:05:21 UTC 
Closing this bug. This quickstart is a WFK quickstart and we do not use bugzilla for them.
Note You need to log in before you can comment on or make changes to this bug.