Re: Maven issue with JDK16 - javac and javadoc

Hi, sorry for the late reply… Enrico I think the latest version should work, and here is the IT (I just didn’t create a PR yet): https://github.com/apache/maven-compiler-plugin/pull/37 MCOMPILER-445/pom.xml succeeds, other tests fail because of an outdated groovy plugin. I will push another commi

Re: Maven issue with JDK16 - javac and javadoc

On 12 Nov 2020, at 14:50, Graham Leggett wrote: > I have been smashing my head against the javadoc plugin and > maven-release-plugin, which keeps failing releases over and over again on the > basis that the docs can’t be built. > > In the absence of a way to fix this, if there is a way to swit

Re: Maven issue with JDK16 - javac and javadoc

I am testing latest build of openjdk16, it seems to me that the problem has been resolved Benjamin, can you please try ? probably there is no need for a fix on Maven Enrico Il giorno lun 14 dic 2020 alle ore 22:12 Benjamin Marwell < bmarw...@apache.org> ha scritto: > > I'm pretty sure this

Re: Maven issue with JDK16 - javac and javadoc

> I'm pretty sure this can be solved without touching the maven startup scripts. > And I don't like the idea to hack the script Agreed. I did not like the idea either, and even worse, I was unable to reproduce the results I had. Am Mo., 14. Dez. 2020 um 21:58 Uhr schrieb Robert Scholte < rfscho

Re: Maven issue with JDK16 - javac and javadoc

I'm pretty sure this can be solved without touching the maven startup scripts. And I don't like the idea to hack the script because one plugin has issues. I expect good help on your question on the jigsaw mailinglist. Robert On 14-12-2020 15:21:04, Benjamin Marwell wrote: I was able to provide a

Re: Maven issue with JDK16 - javac and javadoc

Il giorno lun 14 dic 2020 alle ore 15:21 Benjamin Marwell < bmarw...@apache.org> ha scritto: > I was able to provide a test, but the only solution to the underlying I > found was to modify the mvn start script by adding the missing modules (or > maybe even better: all system modules). > I tried w

Re: Maven issue with JDK16 - javac and javadoc

I was able to provide a test, but the only solution to the underlying I found was to modify the mvn start script by adding the missing modules (or maybe even better: all system modules). >From what I could see from slack, plexus compiler would need to be a module, requiring jdk.javadoc. Thus, we

Re: Maven issue with JDK16 - javac and javadoc

JIRA issue (please kindly review): https://issues.apache.org/jira/browse/MCOMPILER-445 Am So., 13. Dez. 2020 um 14:07 Uhr schrieb Benjamin Marwell < bmarw...@apache.org>: > > If is has proven itself for jlink, then we know we can do the same for > all other tools. > > I tested my PR with a JavaF

Re: Maven issue with JDK16 - javac and javadoc

> If is has proven itself for jlink, then we know we can do the same for all other tools. I tested my PR with a JavaFX app and it did work. But there's no release yet, only the ITs and my test project. But adding a parameter to disable the ToolProvider as a fallback should not be a problem. A tes

Re: Maven issue with JDK16 - javac and javadoc

Yes, that makes a lot of sense. If is has proven itself for jlink, then we know we can do the same for all other tools. If we have a good feeling about the implementation, we could use it at reference for other plugins as some kind of pattern. Robert On 13-12-2020 11:39:02, Benjamin Marwell wro

Re: Maven issue with JDK16 - javac and javadoc

Il Dom 13 Dic 2020, 11:38 Benjamin Marwell ha scritto: > Robert already suggested to use ToolProvider for the JDK9+ builds. I > created such a patch for jlink and I could create s similar one for the > compiler and javadoc plugin. This would solve the underlying problem from > my understanding. >

Re: Maven issue with JDK16 - javac and javadoc

Robert already suggested to use ToolProvider for the JDK9+ builds. I created such a patch for jlink and I could create s similar one for the compiler and javadoc plugin. This would solve the underlying problem from my understanding. As fork mode and fork count would not apply, I would suggest that

Re: Maven issue with JDK16 - javac and javadoc

Is anyone interested in helping with this problem? Otherwise with the advent of jdk16 we will probably see people that need to switch to fork mode for javac, with slower builds, and we will see complaints from users The problem probably is is plexus compiler and the way we start javac, we should

Re: Maven issue with JDK16 - javac and javadoc

Yes, the problem is about javac with "no-fork + -Xdoclint" using no-fork is not a good option because it slows down a lot big multi module projects Enrico Il giorno gio 12 nov 2020 alle ore 13:55 Romain Manni-Bucau < rmannibu...@gmail.com> ha scritto: > @Graham I guess you can force the compile

Re: Maven issue with JDK16 - javac and javadoc

@Graham I guess you can force the compiler to fork and force doclint to none in javadoc plugin config (ensure to use a recent version). Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Gith

Re: Maven issue with JDK16 - javac and javadoc

On 12 Nov 2020, at 14:03, Enrico Olivelli wrote: > I have fallen into this issue about Maven + Maven Compiler Plugin + JDK16 > > This is the issue on JDK issue tracking > https://bugs.openjdk.java.net/browse/JDK-8253996 > > Basically -Xdoclint:missing does not work anymore when you run javac in

Re: Maven issue with JDK16 - javac and javadoc

+1, got some weirdness on j11 too. We should really have a way to ignore these errors, it is too impacting, in particular when javadoc are only deployed to make central or our nexus happy. Romain Manni-Bucau @rmannibucau | Blog

Re: Maven Issue - pluginManagement - build Area Plugin

On 14 Feb 2014, at 08:09, Baptiste Mathus wrote: > Seems like this super pom is versioned at github under the sonatype > organization (?). > > Cf. scm tag in > http://repo1.maven.org/maven2/org/codehaus/codehaus-parent/4/codehaus-parent-4.pom > But https://github.com/sonatype/codehaus-parent giv

Re: Maven Issue - pluginManagement - build Area Plugin

Op Fri, 14 Feb 2014 09:01:14 +0100 schreef Karl Heinz Marbaise : Hi Anders, > I reported this Codehaus parent issue a long time ago (HAUS-2245 [1]). Good to know... Unfortunately the codehaus-parent seems to be in a unmaintained state. Who is responsible for the codehaus-parent ? Can we

Re: Maven Issue - pluginManagement - build Area Plugin

Right. It seems no one knows where the source is. I think this is better to discuss in the JIRA ticket. It's not for this list. I'm sure that e.g. the Mojo team could take responsibility of codehaus-parent. Just need Ben to set up a repo. /Anders On Fri, Feb 14, 2014 at 9:09 AM, Baptiste Mathus

Re: Maven Issue - pluginManagement - build Area Plugin

Seems like this super pom is versioned at github under the sonatype organization (?). Cf. scm tag in http://repo1.maven.org/maven2/org/codehaus/codehaus-parent/4/codehaus-parent-4.pom But https://github.com/sonatype/codehaus-parent gives a 404... Anyone? 2014-02-14 9:01 GMT+01:00 Karl Heinz Ma

Re: Maven Issue - pluginManagement - build Area Plugin

Hi Anders, > I reported this Codehaus parent issue a long time ago (HAUS-2245 [1]). Good to know... Unfortunately the codehaus-parent seems to be in a unmaintained state. Who is responsible for the codehaus-parent ? Can we (or i) take the issue and fix it ? /Anders [1] http://jira.code

Re: Maven Issue - pluginManagement - build Area Plugin

I reported this Codehaus parent issue a long time ago (HAUS-2245 [1]). Unfortunately the codehaus-parent seems to be in a unmaintained state. /Anders [1] http://jira.codehaus.org/i#browse/HAUS-2245 On Wed, Feb 12, 2014 at 9:07 PM, Karl Heinz Marbaise wrote: > Hi, > i have a question. The follo

Re: Maven Issue - pluginManagement - build Area Plugin

Hi, See model builder algorithm [1] If someone codes a version in build/plugin, that mean he wants to override value injected from build/pluginManagement consequence is that once overridden, pluginManagement doesn't apply any more so: defining a version in build/plugin in a global parent pom is

Re: Maven Issue

On Thu, May 12, 2011 at 7:16 PM, Jagadeesh Naidu G wrote: > Thanks in advance  Barrie for helping me. In my parent pom.xml file I > specified junit entry. I am attaching both parent and child pom.xml files. > Thanks & Regards, Your parent pom should not define dependencies. Your parent pom shou

Re: Maven Issue with release:perform

On Thu, May 12, 2011 at 6:11 AM, Jagadeesh Naidu G wrote: >  I am able to build the application successes fully, But while doing mvn > release: perform I am facing one issue with maven. Please help me out how to > fix this issue.  Any help is greatly appreciated. You've now posted the same thing

RE: Maven Issue

2011 1:40 PM To: Jagadeesh Guthikonda Subject: Re: Maven Issue On Thu, May 12, 2011 at 4:26 PM, Jagadeesh Naidu G <[hidden email]> wrote: > Hi I am able to build my application and able to run test cases .i am facing > this issue while doing release only. Did you check whether your p

Re: Maven Issue

On Thu, May 12, 2011 at 4:26 PM, Jagadeesh Naidu G wrote: > Hi I am able to build my application and able to run test cases .i am facing > this issue while doing release only. Did you check whether your pom defines junit? The one you sent didn't look like it did. You may be pulling in junit tran

RE: Maven Issue

Hi I am able to build my application and able to run test cases .i am facing this issue while doing release only. From: Barrie Treloar [via Maven] [mailto:ml-node+4388963-1479824958-207...@n5.nabble.com] Sent: Thursday, May 12, 2011 5:55 AM To: Jagadeesh Guthikonda Subject: Re: Maven Issue On

Re: Maven Issue

On Wed, May 11, 2011 at 3:28 PM, jagadeeshg wrote: > While iam doing release my application iam getting error as below. Please > help me out how to solve this issue. > >  Loading source files for package > com.mtvi.mediabus.anystream.restservices... >        Constructing Javadoc information... >  

Re: Maven Issue

Hi please find the pom.xml below for the above issue. http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> com.mtvi.mediabus

Re: maven issue

On Sun, Mar 27, 2011 at 11:33 PM, zheng.xiaoxi wrote: > Thanks for providing this great Continuous integration tools. But In my > practice, There are two issues: This list (dev@) is meant for discussion about developing the Maven software itself. Please post your questions on the relevant 'user'