No, I do still get those that I quoted earlier, having to do with the generate-sources phase (in your new code generation integration, I’m afraid 😉 )
On 5 May, 2016 at 11:05:48, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
What a pickle. Are sure that what's missing is only
the m2e connectors? That would resolve all the errors, or you still
get some?
Interesting. It turns out that the Tycho Project
Configurators feature was not installed by Oomph in my Eclipse at
all. I must have got it from the m2e connector discovery
catalogue some time ago. The reason why I thought it must
have been Oomphed is that it has persisted through quite a lot of
Oomph-driven p2 installs, and I hadn’t expected that this would
work. I thought Oomph would replace the entire p2 profile of
the installation every time, but it doesn’t; it seems to maintain
bundles that are installed by other means.
So, sorry
about that. I’m not sure now what’s the best way
forward. We can add a few m2e connectors that we need to the
setup model, but the update sites that they pull from are very
version specific (they are not continually accumulating composites
such as Papyrus of the Simultaneous Release) so it seems like a
maintenance pain. And the setup of course doesn’t provide for
automation of the m2e connector discovery installation.
Suggestions?
At any rate, the setup change that I posted to Gerrit for the
maven-helper connector is invalid because it assumes an update site
already known to my installation that a new installation via Oomph
would not have.
On 4 May, 2016 at 14:37:43, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
How come I don't have it if I'm also on my
Oomph-managed Eclipse? Any ideas?
That’s a good question. I have it installed in my
Oomph-managed Eclipse, but it isn’t explicitly referenced by our
setup model, so I supposed it must be a dependency of something
else (perhaps m2e, itself?).
cW
On 4 May, 2016 at 14:26:54, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
I found the org.eclipse.m2e feature
installed, but I don't see the Tycho Project Configurator anywhere.
You say you do have it? From which repository is that supposedly
obtained?
Hi, Ernesto, Céline,
I’ve put up a Gerrit review for the setup model to add the
new m2e connector this is required:
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.
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
_______________________________________________
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
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
_______________________________________________
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
|
