Hi, Ernesto, Céline,
I’ve put up a Gerrit review for the setup model to add the new m2e connector this is required:
https://git.eclipse.org/r/72064
However, we still have some errors that I think go back to the introduction of the code generation integration in the build: Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source (execution: add-source, phase: generate-sources)
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-antrun-plugin: 1.8:run (execution: make, phase: generate-sources)
I don’t know how to fix these. Christian
On 4 May, 2016 at 13:49:07, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
I hit send too soon.
The development .setup includes the m2e plugin:
m2e - Maven Integration for Eclipse (includes
Incubating components) 1.7.0.20160321-2203
org.eclipse.m2e.feature.feature.group Eclipse.org - m2e
After right-clicking on a project -> Maven -> Update
Projects... -> Select all -> OK, it rebuilds but I still get
the errors, and even after a Project->Clean...->All I still
get the same errors, and this is on a freshly installed version. So
that's not enough.
The development setup already installs m2e:
Hello Ernesto,
You should install the m2e plugin that is required to manage
maven plugins.
I don't remember the exact name:
![]()
Then you will be able to make a "Update Project..." from the plugin
menu:
This may update the classpath. But I don't know if we must commit
this kind of change.
HTH
Céline
Le 04/05/2016 à 17:34, Ernesto Posse a
écrit :
I think change 72033 might have been merging too soon.
Now I get a lot of errors in my workbench in almost all
plugins, mostly missing artifacts: e.g.
Description Resource Path Location Type
Missing artifact javax.annotation:jsr250-api:jar:1.0 pom.xml
/org.eclipse.papyrusrt.codegen line 1 Maven Dependency
Problem
Missing artifact aopalliance:aopalliance:jar:1.0 pom.xml
/org.eclipse.papyrusrt.codegen line 1 Maven Dependency
Problem
Missing artifact com.google.guava:guava:jar:14.0.1 pom.xml
/org.eclipse.papyrusrt.xtumlrt.xtext.feature line 1 Maven
Dependency Problem
Missing artifact com.google.inject:guice:jar:3.0 pom.xml
/org.eclipse.papyrusrt.codegen line 1 Maven Dependency
Problem
Missing artifact javax.enterprise:cdi-api:jar:1.0 pom.xml
/org.eclipse.papyrusrt.codegen line 1 Maven Dependency
Problem
and in every pom.xml I get:
On the <parent>:
- Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source
(execution: add-source, phase: generate-
sources)
- Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (execution:
default-compile, phase: compile)
On <packaging>:
- Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-packaging-plugin:0.24.0:validate-id
(execution: default-validate-id, phase: validate)
- Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-packaging-plugin:0.24.0:build-qualifier
(execution: default-build-qualifier, phase: validate)
- Plugin execution not covered by lifecycle configuration:
org.eclipse.tycho:tycho-packaging-plugin:0.24.0:validate-version
(execution: default-validate-version, phase:
validate)
What happened? And how do we fix it?
Do we need to update the Oomph .setup files as well for the
dependencies?
_______________________________________________
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
|