Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Target platform for working on m2e
Exactly as you mentioned the purpose of the target-platform-configuration plugin is only to specify the correct .target file for the Maven build. For your development workspace m2e's Oomph setup takes care of setting that target-file in the preferences. So yes you can safely ignore those missing life-cycle mapping errors (that's probably what I did as well).
 
Regarding your remaining errors about missing packages:
They will vanish with the current Eclipse PDE nightly/snapshot version that will be released with Eclipse 2021-12. Using the Eclipse 2021-12 Milestone 1 build already contains that PDE enhancement.
You can get it if you use the latest (not latest-released) version for your Eclipse product provisioned by the Eclipse Installer (Oomph). When using the latest version of a product it will be updated to the latest milestones/release candidates and not only to the latest releases. That's why the latest version is also used by the m2e Development Environment configuration.
 
Gesendet: Sonntag, 31. Oktober 2021 um 14:13 Uhr
Von: "Alexandros Karypidis via m2e-dev" <m2e-dev@xxxxxxxxxxx>
An: "m2e-dev@xxxxxxxxxxx" <m2e-dev@xxxxxxxxxxx>
Cc: "Alexandros Karypidis" <akarypid@xxxxxxxx>
Betreff: Re: [m2e-dev] Target platform for working on m2e
 
Thanks for your help. Indeed, that has allowed me to at least successfully compile from command-line. I just wanted to make sure everything is in a good state outside Eclipse.
 
Now, regarding my IDE setup: I looked at the plugin documentation (https://www.eclipse.org/tycho/sitedocs/target-platform-configuration/target-platform-configuration-mojo.html) and it seems like all it does is set the tartget platform to the one defined in this maven module:
 
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<configuration>
<target>
<artifact>
<groupId>org.eclipse.m2e</groupId>
<artifactId>target-platform</artifactId>
<version>1.16.0-SNAPSHOT</version>
</artifact>
</target>
 
So if I checked to see the target platform that is selected in the preferences (PDE -> Target Platform) and that seems to be the case anyway (some setup tasks run at startup to do this). I think that means I can safely mark them as ignored.
 
This leaves me though with 3 errors in my workspace:
 
Package 'META-INF.plexus' does not exist in this plug-in MANIFEST.MF /org.eclipse.m2e.archetype.common/META-INF line 67 Plug-in Problem
 
Package 'META-INF.plexus' does not exist in this plug-in MANIFEST.MF /org.eclipse.m2e.maven.runtime/META-INF line 327 Plug-in Problem
 
Package 'META-INF.sisu' does not exist in this plug-in MANIFEST.MF /org.eclipse.m2e.maven.runtime/META-INF line 328 Plug-in Problem

Anyone can help sort these out? I'm, not familiar with these. Looks like some "special names" that probably don't really represent specific dependencies?
 
 
Στις Κυριακή, 31 Οκτωβρίου 2021, 10:49:47 π.μ. GMT, ο χρήστης Hannes Wellmann <wellmann.hannes1@xxxxxxx> έγραψε:
 
 
Hello
 
the "Plugin execution not covered by lifecyle configuration" errors also occured for me a while ago but did not stay for long (I don't remember anymore if I did something or if they just vanshied), however they should not be harmfull.
If this error persists and is a problem for you, maybe Mickael Istra or Christoph Läubrich can help you better because they are more involved into Tycho.
 
Regarding your command-line build problem:
 
The build command in the CONTRIBUTING guide is indeed incomplete. The -Dtycho.mode=maven property is missing. So the two commands should be:
 
    mvn generate-sources -f m2e-maven-runtime -Pgenerate-osgi-metadata -Dtycho.mode=maven
    mvn clean verify
 
I have just updated the CONTRIBUTING.md (see https://github.com/eclipse-m2e/m2e-core/pull/390).
Alternatively you can use the pre-configured launch configs mentioned in the CONTRIBUTING.md to build m2e from the Eclipse-IDE.
 
Best regards,
Hannes
 
 
Gesendet: Samstag, 30. Oktober 2021 um 20:54 Uhr
Von: "Alexandros Karypidis via m2e-dev" <m2e-dev@xxxxxxxxxxx>
An: "m2e-dev@xxxxxxxxxxx" <m2e-dev@xxxxxxxxxxx>
Cc: "Alexandros Karypidis" <akarypid@xxxxxxxx>
Betreff: [m2e-dev] Target platform for working on m2e
Hi all,
 
I'm an occassional Eclipse contributor. There's a bug in m2e I want to work on and I was setting up my development environment (it's been a while since I last worked on m2e). I'm following the instructions in m2e-core/CONTRIBUTING.md at master · eclipse-m2e/m2e-core
 
After running the eclipse installer, I got Eclispe running with a workspace that has m2e-core / m2e-core-tests / m2e-maven-runtime cloned. Unfortunately even after restarting / updating maven projects, the target platform is missing so I get errors in some projects as follows:
 
Plugin execution not covered by lifecycle configuration: org.eclipse.tycho:target-platform-configuration:2.5.0:target-platform (execution: default-target-platform, phase: initialize) 
 
 
I see that the installer has added the Tycho project configurators but I suppose there is no m2e connector for this particular one? Do I need to manually point somewhere? The catalog in the installation seems to be the defaultl:
 
 
Further to this, I can't seem to compile even from command line. Supposedly I need to first run:
 
    mvn generate-sources -f m2e-maven-runtime -Pgenerate-osgi-metadata
    mvn clean verify
 
Unfortunately the first command fails for me with:
 
$ mvn generate-sources -f m2e-maven-runtime -Pgenerate-osgi-metadata
[INFO] Scanning for projects...
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse.m2e:target-platform:target:1.16.0-SNAPSHOT -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse.m2e:target-platform:target:1.16.0-SNAPSHOT
 
Have I missed a step?
_______________________________________________ m2e-dev mailing list m2e-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
 
 
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________ m2e-dev mailing list m2e-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
 
 

Back to the top