Prepare 4.38 development

[eclipse-releng-bot]

Prepare development of Eclipse 4.38.
This complements:

• Prepare 4.38 development eclipse-platform/eclipse.platform.releng.aggregator#3271

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 7a38878. ± Comparison against base commit 1b0164f.

[HannesWell]

The build currently fails with:

 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:5.0.0-SNAPSHOT:compare-version-with-baselines (compare-attached-artifacts-with-release) on project org.eclipse.jdt.core.compiler.batch: Baseline and reactor have the same fully qualified version, but different content
 [ERROR] different
 [ERROR]    META-INF/ECLIPSE_.RSA: not present in baseline
 [ERROR]    META-INF/ECLIPSE_.SF: not present in baseline
 [ERROR] -> [Help 1]

My first guess is that it's somehow connected to the configuration in the pom.xml:

eclipse.jdt.core/org.eclipse.jdt.core.compiler.batch/pom.xml

Lines 76 to 92 in 1b0164f

	<plugin>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-p2-plugin</artifactId>
	<configuration>
	<baselineMode>${compilerBaselineMode}</baselineMode>
	<baselineReplace>${compilerBaselineReplace}</baselineReplace>
	</configuration>
	<executions>
	<execution>
	<id>attached-p2-metadata</id>
	<phase>package</phase>
	<goals>
	<goal>p2-metadata</goal>
	</goals>
	</execution>
	</executions>
	</plugin>

But it's of course the question why this only now a problem.

[HannesWell]

But it's of course the question why this only now a problem.

Looking into this, I don't understand why this happens at the moment. But as this also happened the last time and as far as I can tell, everything went well afterwards, I assume it's a temporary problem:

• Prepare 4.37 development #4066 (comment)

Can a JDT committer please submit this?

[HannesWell]

Can a JDT committer please submit this?

@iloveeclipse, @akurtakov, @stephan-herrmann. It would be great if you or anybody else could have quick lock, as this is the last submodule to update before we can run the first I-build of the new stream.