Maven Compiler Plugin 3.8.0 incompatibility

[ddugovic]

Similar to #46 but I'm attempting to update this plugin without downgrading Maven:

Failed to execute goal com.alexnederlof:jasperreports-plugin:2.4:jasper (default) on project base: The plugin com.alexnederlof:jasperreports-plugin:2.4 requires Maven version 3.5.0

[brunoabdon]

Maybe we should create a fork for backward compatibilities.

Jasper-report-maven-plugin-backport would try to keep most of the latest releases functionalities while running with the lowest ever possible versions of its dependencies, of Maven and of Java itself.

It's not at all uncommon for old legacy system to be improved by just adding new reports (I say that from my own experience: #36).

I would volunteer for that.

[alexnederlof]

downgrading Maven:

You mean upgrading? because it's backward compatible, but not the other way around.

Maybe we should create a fork for backward compatibilities.

That should be easy enough to do. In this commit fca2ada I switch to the annotation api, which is not backwards compatible with older Maven versions. If you would revert that change, and then re-apply the changes since, you would have your older version.

If you are willing to maintain it, I can make you a project member and we could do that in a separate branch, and separate release version scheme, if there are more people that want it. Although I wonder how many people don't update their Maven regularly, because AFAIK it's always been backward compatible.

[ddugovic]

Sorry, you are correct; I had confused the Eclipse Maven plugin connector version with the compiler version. Thanks for the advice in case I need to fork/branch; hopefully soon my team will upgrade to the latest Eclipse release (currently using Oxygen.3) but if it ends up taking months for us to upgrade, I'll probably fork this (without an intent to do long-term support).