Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] oomph installer upgrade

Christian,

Thanks for this element.

I will look with Camille if it has an interest to include them also at the level of development-time workbench.

Because it could be good that after installation of the development environment with Oomph that we have a fully setup environment where we can also use the code generation additional developer plugins.

I will keep you in touch.

Sincerely,

Francois

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : mardi 14 octobre 2014 14:06
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] oomph installer upgrade

 

Hi, François,

 

Thanks for your interest in the Oomph installer.  I'm glad that it has been helpful to you.

 

On the subject of the management of SSH keys, this would be in the domain of the Oomph tooling, not a particular setup model such as the Papyrus setup model.  Please ask questions about that in the Oomph forum (newsgroup).

 

Those additional developer plug-ins are imported by the "Papyrus / Developer" project in the setup model.  Did you select that for import when you created your workspace?  This brings them into your workspace, so that they are available for code generation activities in a run-time workbench (not your development-time workbench).  To install them into the development-time workbench would require that they be built and deployed in a p2 repository, but I don't think that such is available.

 

Cheers,

 

Christian

 

On Oct 14, 2014, at 7:45 AM, LE FEVRE François 218080 <francois.le-fevre@xxxxxx> wrote:



Dear papyrus team,

I am newbie to the papyrus community. So I have started with the oomph installer to have a fully compatible developer environment.

It is a great tool!

 

Nevertheless, I have noticed two points that could perhaps be upgraded:

 

SSH

When configuring the oomph installer, I have initially chosen the ssh git configuration.

Badly, it seems that Eclipse Oomph where not able to get the key that was store in my .ssh folder.

So I had to switch to https configuration and then after installation I have switched back to ssh configuration with manual import of my key (windows>preference>ssh)

 

>>Perhaps it could be good to allow to reference specific ssh key in the oomph installer?

 

GMF

My first job was to make a small enhancement in the use case diagram (https://bugs.eclipse.org/bugs/show_bug.cgi?id=446853)

I was in difficulty since I could not open the /org.eclipse.papyrus.uml.diagram.usecase/models/usecaseDiagram.gmfgen.

So I have followed advices of Patrick T. to import manually additional developer plugins.

>>Perhaps it could be good to add them for default in the oomph installer?

 

I have downloaded:

-GMF tooling, runtime,notation SDK and xtend2 support

-Xtext complete sdk

 

I have used the following update sites (but I had to make several times the update since of plugin update problems)

 

Sincerely,

 

 

 

François Le Fèvre

NANO-INNOV

CEA Tech/LIST/DILS

91191 GIF SUR YVETTE

0169084986

-

 

_______________________________________________
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

 


Back to the top