Re: Maven Plugin Plugin (get rid of javadoc taglet?)

2018-10-03 Thread Olivier Lamy
On Thu, 4 Oct 2018 at 02:29, Robert Scholte wrote: > I asked the same question last week. > Oops sorry my bad I missed that > My conclusion: remove doclettags. > good point > However, I'd like to stay on 3.x so the '3' reflects that this plugin > requires at least Maven 3. > fair enough >

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Tibor Digana
It makes a logical sense to me to remove JDK 9 and 10. To be honest, we should perhaps lookup those Jira issues which appear only in 9 and not in some higher version. On Wed, Oct 3, 2018 at 6:41 PM Robert Scholte wrote: > I don't think we will get a lot of *new* reds, only those related to ASM.

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Robert Scholte
I don't think we will get a lot of *new* reds, only those related to ASM. And this is probably the time to make all projects Java 11 ready, the first complaints are already coming in. On Wed, 03 Oct 2018 10:56:28 +0200, Olivier Lamy wrote: hehe we may see a lot of red :) On Wed, 3 Oct

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Robert Scholte
0: the versions are available and it makes our message to the community a lot easier: it all works with Java 7 and above. And what do we really gain? The more different versions we test with, the more we can confirm the stability. I don't expect tests to fail only for 9 or 10. On the other

Re: Maven Plugin Plugin (get rid of javadoc taglet?)

2018-10-03 Thread Robert Scholte
I asked the same question last week. My conclusion: remove doclettags. However, I'd like to stay on 3.x so the '3' reflects that this plugin requires at least Maven 3. It's a matter of good release notes and documentation, but I expect (and hope) only a few will notice these missing

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Sylwester Lachiewicz
+1 On Wed, Oct 3, 2018, 12:11 PM Olivier Lamy wrote: > +1 > > On Wed, 3 Oct 2018 at 20:06, Michael Osipov wrote: > > > I'd boldly drop 9 and 10, they're dead. > > > > Am 2018-10-03 um 10:56 schrieb Olivier Lamy: > > > hehe we may see a lot of red :) > > > > > > On Wed, 3 Oct 2018 at 15:46,

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Olivier Lamy
+1 On Wed, 3 Oct 2018 at 20:06, Michael Osipov wrote: > I'd boldly drop 9 and 10, they're dead. > > Am 2018-10-03 um 10:56 schrieb Olivier Lamy: > > hehe we may see a lot of red :) > > > > On Wed, 3 Oct 2018 at 15:46, wrote: > > > >> This is an automated email from the ASF dual-hosted git

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Michael Osipov
I'd boldly drop 9 and 10, they're dead. Am 2018-10-03 um 10:56 schrieb Olivier Lamy: hehe we may see a lot of red :) On Wed, 3 Oct 2018 at 15:46, wrote: This is an automated email from the ASF dual-hosted git repository. rfscholte pushed a commit to branch master in repository

Maven Plugin Plugin (get rid of javadoc taglet?)

2018-10-03 Thread Olivier Lamy
Hi, I'm trying to build maven-plugin-plugin with jdk11. But yup this will not work with import com.sun.javadoc.Tag; import com.sun.tools.doclets.Taglet; etc... There is even some javax.swing usage... (well mainly to use only some data structure). I guess in 2018 everyone is now using the

Re: [maven-jenkins-lib] branch master updated: Add Java 11 to defaults

2018-10-03 Thread Olivier Lamy
hehe we may see a lot of red :) On Wed, 3 Oct 2018 at 15:46, wrote: > This is an automated email from the ASF dual-hosted git repository. > > rfscholte pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git > > > The following commit(s) were