I would have reopened MJAR-235, because effectively there's no change. But
that's a matter of taste.
It's fine like this,
Robert
On Sat, 15 Apr 2017 13:04:41 +0200, Karl Heinz Marbaise
wrote:
Hi,
On 15/04/17 13:02, Robert Scholte wrote:
Thanks,
not sure if this is
Hi,
On 15/04/17 13:02, Robert Scholte wrote:
Thanks,
not sure if this is worth a separate jira-issue, because IMHO it will
pollute the release notes a bit. But that's another topic.
But it makes clear why this change has been made and the detailed
explanation...
Kind regards
Karl Heinz
Thanks,
not sure if this is worth a separate jira-issue, because IMHO it will
pollute the release notes a bit. But that's another topic.
Robert
On Sat, 15 Apr 2017 12:58:25 +0200, Karl Heinz Marbaise
wrote:
Hi Robert,
Done. See MJAR-236..
Kind regards
Karl Heinz
Hi Robert,
Done. See MJAR-236..
Kind regards
Karl Heinz
On 15/04/17 12:44, Robert Scholte wrote:
Hi Karl Heinz,
I'd prefer to leave maven-compiler-plugin on 3.5.1 as default.
The 3.6.x have Java 9 features which are not optimal yet. E.g. in some
circumstances we should warn the developer
Hi Robert,
On 15/04/17 12:44, Robert Scholte wrote:
Hi Karl Heinz,
I'd prefer to leave maven-compiler-plugin on 3.5.1 as default.
The 3.6.x have Java 9 features which are not optimal yet. E.g. in some
circumstances we should warn the developer about automodules. If this
version becomes the
Hi Karl Heinz,
I'd prefer to leave maven-compiler-plugin on 3.5.1 as default.
The 3.6.x have Java 9 features which are not optimal yet. E.g. in some
circumstances we should warn the developer about automodules. If this
version becomes the default, it is more likely to have issues with our