Use the main project to let bnd compute the output file

[laeubi]

Currently we compute the name of the subjar manually, but this can be overridden by the user so it is better to let bnd calculate the file itself.

FYI @chrisrueger

[chrisrueger]

I can confirm that this PR fixes our build which has set:

target-dir=generated${if;${driver;eclipse};;/${driver}}

(see related https://bnd.bndtools.org/chapters/150-build.html#avoiding-target-dir-conflicts-between-different-build-tools )

Only thing I noticed is that it generates a folder generated/unset/

I believe unset is from the ${driver} above which does seem to be populated with 'unset' or is not set. Not sure that is intended or correct. It seems that Eclipse identifies itself as eclipse. Not sure if it is possible that tycho populates it with eclipsetycho?

The idea behind this is that each build tool writes into its own folder so that different build tools (drivers) do not step on eachothers toes.

This seems how bnd gets and sets the driver:

• https://github.com/bndtools/bnd/blob/0e76ec64a8a561c8282c35010543c4f1d698e3bb/biz.aQute.bndlib/src/aQute/bnd/build/Workspace.java#L1120

Gradle plugin seems to set it here:
https://github.com/bndtools/bnd/blob/master/gradle-plugins/biz.aQute.bnd.gradle/src/main/java/aQute/bnd/gradle/BndWorkspacePlugin.java#L169

[github-actions]

Test Results

  606 files  ±0    606 suites  ±0   4h 13m 45s ⏱️ + 4m 16s
  434 tests ±0    426 ✅ ±0   7 💤 ±0  1 ❌ ±0 
1 302 runs  ±0  1 278 ✅  - 1  22 💤 ±0  2 ❌ +1 

For more details on these failures, see this check.

Results for commit b63700a. ± Comparison against base commit 6d565f3.

♻️ This comment has been updated with latest results.

[laeubi]

The driver name is now init with "tycho-maven-build"

[eclipse-tycho-bot]

💚 All backports created successfully

Status	Branch	Result
✅	tycho-4.0.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details