[Build] Specify options for the build JVM only in Jenkins pipeline

[HannesWell]

The options where introduced for all builds of the p2 repo via #464

Having it enabled can cause problems in GitHub workflows that are sensitive to the printout.

[laeubi]

Having it enabled can cause problems in GitHub workflows that are sensitive to the printout.

Should then not better the GitHub workflows be fixed? I'm not sure that one should depend on any special output of the build pipeline...

[HannesWell]

Having it enabled can cause problems in GitHub workflows that are sensitive to the printout.

Should then not better the GitHub workflows be fixed?

I think both is appropriated, as mentioned in #558 (comment)

For the GH workflows to build P2 e.g. the Xmx config is not necessary.

I'm not sure that one should depend on any special output of the build pipeline...

In hindsight this wasn't the best idea, but I followed to example given to me in eclipse-platform/eclipse.platform.releng.aggregator#2352 (comment) without thinking about this case. :)

[github-actions]

Test Results

  375 files  ±0    375 suites  ±0   43m 14s ⏱️ +54s
1 895 tests ±0  1 892 ✅ ±0  3 💤 ±0  0 ❌ ±0 
6 685 runs  ±0  6 676 ✅ ±0  9 💤 ±0  0 ❌ ±0 

Results for commit 361b345. ± Comparison against base commit e55cc8f.

[laeubi]

For the GH workflows to build P2 e.g. the Xmx config is not necessary.

I think its always good to have Jenkins + Github as close as possible to verify things on different platforms.

[HannesWell]

For the GH workflows to build P2 e.g. the Xmx config is not necessary.

I think its always good to have Jenkins + Github as close as possible to verify things on different platforms.

In general yes, but since these options were just added to fix failures on Jenkins I'm not sure if it might be better to just apply it to Jenkins. Especially since it now clutters all other builds.

What are the opinions of the others?
To fix the version-increment workflow this is not necessary anymore.

[HannesWell]

Ok, let's keep it as it is for now.