[MTOOLCHAINS-29] Possibility not to fail if toolchain.xml is not available

[jira-importer]

Hüseyin Kartal opened MTOOLCHAINS-29 and commented

In development environment we face the problem of multiple jdk's. But also some environments are setup for single jdk's like in CI/CD.

In these environments we don't supply a toolchain.xml. But the project pom.xml has a toolchain plugin configuration with the needed jdk and fails therefore.

A possibility to tell toolchain just to warn without fail in these environments would be very convenient. Maybe like the enforcer-plugin https://maven.apache.org/enforcer/maven-enforcer-plugin/enforce-mojo.html#fail

---

Affects: 1.1

Remote Links:

• GitHub Pull Request #3
  

[jira-importer]

Robert Scholte commented

This seems to be a valid reason to use profiles. By default you won't have toolchains, but when activating the ci-profile (which contains the maven-toolchain-plugin) you can/must use the preferred toolchain.
If you need help for this, we could turn this into an example on the plugin webpage.

[jira-importer]

Hüseyin Kartal commented

Well on the CI we don't need to use the toolchain. Because we use the image with the fitting tools. And we also use the enforcer plugin to check (but not fail). But on developer environments there could be more not fitting tools. Like JDK9+ wich will already fail with JDK8 projects.

The changes of jdk9+ made the toolchain essencial again, But i am sure mostly, a warning would be enough. At the first place the toolchains-plugin should provide the ability to share configuration, not to enforce. This job does the enforcer plugin quite well with a great set of built-in rules.

I could imagine that it is maybe posible to switch jdk just by using profiles, even without toolchain. But that would just blow up the POM. And it is the same with your consideration to enable or disable toolchain by profiles.

Just because there is a workaround, This feature shouldn't rejected.

Despite of the last release, the toolchain plugin just didn't developed for a long time. This would be a nice movement to get more similarity to enforcer plugin.

This is an optional convenient and common (enforcer-plugin) feature. So come on.