Bug 1305579

Summary: Ability to change/specify default folder names when creating a new Teiid Model project
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Cojan van Ballegooijen <cojan>
Component: Teiid DesignerAssignee: Barry LaFond <blafond>
Status: CLOSED DEFERRED QA Contact: Matus Makovy <mmakovy>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: drieden, jolee, mbaluch, vhalbert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-09 08:55:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of Model Project Options wizard step when creating a new Teiid Model Project none

Description Cojan van Ballegooijen 2016-02-08 15:50:10 UTC
Created attachment 1122188 [details]
Screenshot of Model Project Options wizard step when creating a new Teiid Model Project

Description of problem:
The new Teiid Model project wizard let you create default folders called sources,views,schemas,web_services, one can changes these during the creating of a new Teiid Model project but would like to have the ability to change these upfront through either a config file (i.e. jbdevstudio.ini) or in the Teiid Designer preferences of JBoss Developer Studio

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


How reproducible:


Steps to Reproduce:
1. Create a new Teiid Model Project
2. Name the project
3. press Next
4. Model Project Options window appears
sources
views
schemas
web_services folder names are displayed as default


Actual results:
See steps to reproduce

Expected results:
Ability to change the default values of the folder names

Additional info:

Comment 2 Matus Makovy 2016-02-09 08:55:00 UTC
We are tracking tooling issues in JIRA, so I replicated this to JIRA (TEIIDDES-2778) and I will close this.