Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 284019 - [Wizard] creating new Xpand project should use settings from preferences
Summary: [Wizard] creating new Xpand project should use settings from preferences
Status: CLOSED FIXED
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: 0.7.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 299099
Blocks:
  Show dependency tree
 
Reported: 2009-07-20 11:18 EDT by ekkehard gentz CLA
Modified: 2013-02-21 08:10 EST (History)
3 users (show)

See Also:
sven.efftinge: helios+

Attachments
Screenshot of the wizard (47.61 KB, image/jpeg)
2010-01-05 09:57 EST, Darius Jockel CLA 		no flags Details
An alternative Xpand project wizard (4.76 KB, patch)
2010-01-05 10:00 EST, Darius Jockel CLA 		no flags Details | Diff
An alternative Xpand project wizard (20.25 KB, patch)
2010-01-06 02:38 EST, Darius Jockel CLA 		no flags Details | Diff
Unwanted project-specific settings, when using workspace defaults (76.65 KB, image/png)
2010-01-08 03:16 EST, Sven Efftinge CLA 		no flags Details
An alternative Xpand project wizard (19.46 KB, patch)
2010-01-08 04:11 EST, Darius Jockel CLA 		sven.efftinge: iplog+
Details | Diff
Show Obsolete (2) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ekkehard gentz CLA 2009-07-20 11:18:59 EDT 
If you create a new Xpand project, then the project properties of Xtend/Xpand are always set to
Activated Metamodel Contributors: EMF Metamodels

Same happens if Adding Xtend/Xpand Nature to a project.

But there should be used the values and order from Preference settings,
where in my case was:
UML2 profiles
EMF Metamodels

I also tried checking / unchecking "project-specific" and "restore Defaults",
but no way to get my Preferences settings as default into my project properties

if the project is a converted oaw4 project then "Add Xtend/Xpand Nature" should test if its an old oaw4 project and use the same settings - if possible -
Comment 1 Peter Friese CLA 2009-07-20 11:33:24 EDT 
I agree, a new project should use the workspace settings as its default settings. That's how the JDT operates as well.

Regarding the second issue (converting old projects): as you will only convert a project once I am not sure if it worth the effort to provide code that constantly checks if this is an oAW 4 project and tries to translate the project settings. You'll have to perform a number of migration steps anyway, so providing too much comfort might leave the impression that migrating from oAW 4 to Eclipse Modeling comes at no cost. If we venture into this, we'd need to provide a full-blown migration wizard which definitely is a huge chunk of work (and needs to be re-done for each new version of the frameworks).
Comment 2 ekkehard gentz CLA 2009-07-20 12:08:53 EDT 
Peter,
you're right - conversion is only done once, so its not so important,
only wanted to ask about it ;-)
ekke
Comment 3 Darius Jockel CLA 2010-01-05 09:57:19 EST 
Created attachment 155333 [details]
Screenshot of the wizard
Comment 4 Darius Jockel CLA 2010-01-05 10:00:16 EST 
Created attachment 155334 [details]
An alternative Xpand project wizard
Comment 5 Darius Jockel CLA 2010-01-05 10:07:20 EST 
(In reply to comment #3)
> Created an attachment (id=155333) [details]
> Screenshot of the wizard

Please take a look at the alternative Xpand project wizard.
The wizard has now a new section "metamodels".
inside the section it is possible to select one of the three options:
-Use metamodels defined in workspace
-Use project specific metamodels
-Create an, EMF-based, example project.

Feedback is appreciated

Regards
Darius
Comment 6 Sebastian Zarnekow CLA 2010-01-05 10:08:31 EST 
The attached patch does not seem to be related to this bug.
Comment 7 Darius Jockel CLA 2010-01-06 02:38:06 EST 
Created attachment 155394 [details]
An alternative Xpand project wizard
Comment 8 Darius Jockel CLA 2010-01-06 02:40:55 EST 
(In reply to comment #6)
> The attached patch does not seem to be related to this bug.

Sorry,
I have uploaded the correct patch.

Regard,
Darius
Comment 9 Sven Efftinge CLA 2010-01-08 03:16:14 EST 
Created attachment 155574 [details]
Unwanted project-specific settings, when using workspace defaults
Comment 10 Sven Efftinge CLA 2010-01-08 03:17:28 EST 
Looks good. But it seems that the workspace default wizard still creates a project specific setup, but just copies the workspace configuration. It should do nothing, but adding the nature. No project-specific xpand preferences. (see screenshot)
Comment 11 Sven Efftinge CLA 2010-01-08 03:24:50 EST 
See also #299099
Comment 12 Darius Jockel CLA 2010-01-08 04:11:02 EST 
Created attachment 155580 [details]
An alternative Xpand project wizard
Comment 13 Sven Efftinge CLA 2010-01-28 09:40:43 EST 
patch applied. Thanks!
Comment 14 Karsten Thoms CLA 2013-02-21 08:10:24 EST 
Bug resolved before Xpand 1.2 release date => Closing