Re: [mdt-papyrus.dev] Oomph Setup Changes

[Andrew Eidsness <eclipse@xxxxxxxxxx>]

Ahhh, that is great thanks!  I also had two stale entries in my installer (from previously aborted attempts), that I'm
now able to get rid of.

If anyone else tries to edit this file, beware that my changes weren't noticed until after I restarted the installed
IDE.  I probably should have made the changes without it running.

-Andrew

On 14-07-28 06:57 AM, MAGGI Benoit wrote:
> Hi Andrew,
> 
> The oomph configuration for personal setup is in an .eclipse directory in your user directory.
> For example here on windows : C:\Users\bmaggi\.eclipse\org.eclipse.oomph.setup\setups 
> 
> I got this line : 
>   <project href="file:/C:/git/papyrus/releng/org.eclipse.papyrus.oomph/setups/papyrus.setup#/"/>
> 
> Regards,
> Benoit Maggi
> 
> -----Message d'origine-----
> De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Andrew Eidsness
> Envoyé : lundi 28 juillet 2014 12:52
> À : mdt-papyrus.dev@xxxxxxxxxxx
> Objet : Re: [mdt-papyrus.dev] Oomph Setup Changes
> 
> This sounds like a good idea, how do I get it?
> 
> I originally put the papyrus.setup model into Oomph by dragging/dropping the file.  Should Oomph now have some idea where that file exists in the repo in order to get updates?  Or maybe I need to drag/drop again?  If I do need to drag/drop again, then should I use a dialog that I opened from my IDE, or is it better to run the Oomph installer
> (setup-eclipse) again?
> 
> -Andrew
> 
> On 14-07-27 03:12 PM, Christian W. Damus wrote:
>>
>> Hi, Team,
>>
>> For those of you who have been using the Papyrus set-up model for 
>> Oomph (and I thank you for your bleeding-edge test effort!), you 
>> should know that there has been a fairly significant change in the set-up model that may affect your subsequent installs/updates of your Oomph-managed Papyrus IDEs.
>>
>> The Papyrus set-up model now makes use of the recently introduced 
>> standard "Target Platform" variable to greatly simplify the 
>> definitions of the various Papyrus components in the model.  In particular, this eliminates the need for mass replication of variables in every stream of every component sub-project.  Yay!
>>
>> However, it does mean that in order for your set-up to work correctly, 
>> you now must ensure that this new variable is correctly provisioned in 
>> your environment.  For development of the Papyrus code, which is 
>> currently Luna version (maintenance), you must set your Target 
>> Platform variable to "Luna" as shown below.  Note that you may have to select the "Show all variables" checkbox to see this variable if you have already assigned it some value (which you may have done because we didn't previously use it).
>>
>> The benefit of this variable is that, as it is adopted by other 
>> projects (EMF already has, for example), it makes it easy to ensure a 
>> consistent target platform that will work for all of the projects that you work on in any given Oomph-managed workspace.
>>
>> Cheers,
>>
>> Christian
>>
>>
>>
>>
>> _______________________________________________
>> mdt-papyrus.dev mailing list
>> mdt-papyrus.dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or 
>> unsubscribe from this list, visit 
>> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>>
> 
> _______________________________________________
> mdt-papyrus.dev mailing list
> mdt-papyrus.dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
> _______________________________________________
> mdt-papyrus.dev mailing list
> mdt-papyrus.dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>