Re: [papyrus-rt-dev] New problem with Oomph developer setup

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

Hi Christian. I didn't run the setup from an existing workbench. I ran the Eclipse installer and selected the Papyrus-RT components, and selected new folders for the installation the workspace and the git repo. Is there any other folder that might be getting junk? A user-level folder? Something under ~/.eclipse or ~/.p2?

As for the errors, it is weird that you get those errors only on the codegen stuff and I get them in all projects, although the exact errors seem different, both are about the plugin execution not covered by the lifecycle.

I found this online:

http://stackoverflow.com/questions/6352208/how-to-solve-plugin-execution-not-covered-by-lifecycle-configuration-for-sprin 

Maybe we need to add that to our poms?

But even then that doesn't explain why you and I get different errors. 

Celine: do you get any errors on the codegen projects?

On Mon, May 9, 2016 at 12:21 PM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Ernesto,

Nothing has changed in the working-set definitions in some while and they seem to work for me.  I deleted all of the working-sets from my workspace's Oomph workings-sets model, ran the Oomph setup with only the working-set tasks selected, and this is the result:

Perhaps your working-set model has some junk left-over from earlier iterations of the setup model and could use a similar cleaning?  It’s especially a problem if you imported the setup from various of its previous locations, because the working-set model will have repeated references to the same definitions in the various instances of the setup model reachable through its different historical URIs (local filesystem, http-git, the Papyrus-RT website, etc.)  Henceforward, with the setup at a stable URI, the replication problem should not recur.

The Tycho Projects Configurator is just another of the connectors in the Maven Connector Discovery thing launched from the preferences.  If you don’t see it there, then probably you already have it installed.  I haven’t had a chance to think again about how best to include these connectors in the set-up (the repositories that host them are so very specific to each micro-version that maintenance will be a pain).

The problems that I get with the Tycho Projects Configurator and Maven Build Helper connectors installed are attached.

Christian

On 9 May, 2016 at 11:44:39, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:

I tried the developer setup again after updating Oomph this morning and there seems to be an additional problem. The worksets for "Releng" and "Features" are empty and their projects are left under "Other Projects". Perhaps something in the update changed the rules of how projects are matched?

By the way, any news regarding the m2e problems? 

Celine: I installed the m2e connector for build-helper-maven-plugin but I don't know where to obtain the "Tycho Project Configurator" plugin, and Christian says that even with those there still is a problem.

Christian: you mentioned there was a problem with the poms in my new code generation integration. Which poms? I get "plugin execution not covered by lifecycle configuration" errors, but I get those in every project, except for the XtUMLRT and the JUnit framework projects. Are these the same errors you get?

--

Ernesto Posse

Zeligsoft

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev