Maven javadoc plugin ignores custom tags - maven-javadoc-plugin

Although the build was started using java version: 1.8.0_242, vendor: AdoptOpenJDK, I'm getting the warning -tag option is not supported on Java version < 1.4. When building with javadoc:jar, the build fails because of the custom tags.
This is a quite old build using maven-javadoc-plugin:2.10.4. I cannot just ramp it up to 3+, and 2.10.4 seems to be newest version of 2.10.
Any ideas?

Related

Found Gradle version Gradle 7.4. Versions Gradle 6.0.0 and newer are not supported in FG3, FG4 however supports Versions 6.8.1 and newer

I have a problem with Gradle. I'm trying to make a mod for Minecraft 1.12.2 and I'm using Intellij IDEA. Everything works fine for the version 1.16.4, but if I want to build a mod for the 1.12 I get this error:
Failed to apply plugin 'net.minecraftforge.gradle'.
Found Gradle version Gradle 7.4. Versions Gradle 6.0.0 and newer are not supported in FG3, FG4 however supports Versions 6.8.1 and newer. Consider upgrading.
It's supposed to do something with apply plugin: 'net.minecraftforge.gradle' in the build.gradle file.
I don't have much experience with this sort of stuff so please help me. Thanks in advance
to write a mod for 1.12.2, Forge provides a build.gradle file. In this, the 3.+ (FG3) is specified as the ForgeGradle version.
The current version of Gradle (7.4.2) only supports ForgeGradle versions from FG4 and newer.
FG3 - older than Gradle version 6.0.0
FG4 - Gradle version 6.8.1 and newer
You now have two options:
You take the Gradle version 7.4.2 and make a mod for a Minecraft version with a ForgeGradle version from FG4 or newer.
You take an older Gradle version.

which version of sonarqube gradle plugin compatible with jdk 7?

I am trying to integrate sonarqube gradle plugin with jdk7 but build is failing due to version mismatch.
Gralde version 4.3
JDK 1.7
Sonarqube-gradle plugin ??
2.0.1 was the last version to support Java 7
https://github.com/SonarSource/sonar-scanner-gradle/releases/tag/2.0.1
https://github.com/SonarSource/sonar-scanner-gradle/blob/2.0.1/build.gradle#L24..L25

How does the Gradle wrapper determine which Groovy version it's using?

This question doesn't mention the wrapper.
OS is Linux Mint 18.3.
So for this project I get the following from the wrapper:
mike#M17A ~/software projects/eclipse-workspace/TM_Engine_Exp $ ./gradlew -version
------------------------------------------------------------
Gradle 5.4.1
------------------------------------------------------------
Build time: 2019-04-26 08:14:42 UTC
Revision: 261d171646b36a6a28d5a19a69676cd098a4c19d
Kotlin: 1.3.21
Groovy: 2.5.4
Ant: Apache Ant(TM) version 1.9.13 compiled on July 10 2018
JVM: 11.0.4 (Ubuntu 11.0.4+11-post-Ubuntu-116.04.1)
OS: Linux 4.4.0-53-generic amd64
From the OS I get the following (NB I know this is irrelevant!):
mike#M17A ~ $ groovy -version
WARNING: An illegal reflective access operation has occurred
...
Groovy Version: 2.5.8 JVM: 11.0.4 Vendor: Ubuntu OS: Linux
(NB the warning here occurs if you use a JDK > 8: there's nothing you can do about it currently).
And I get the following for the system's Gradle version (again irrelevant):
mike#M17A ~ $ gradle -version
WARNING: An illegal reflective access operation has occurred
...
------------------------------------------------------------
Gradle 4.8.1
------------------------------------------------------------
...
Groovy: 2.4.12
...
But my build.gradle contains the following dependency currently:
apply plugin: 'groovy'
...
dependencies {
compile 'org.codehaus.groovy:groovy-all:2.5.7'
...
My environment variable is:
GROOVY_HOME=/home/mike/.sdkman/candidates/groovy/current
I'm not sure how this came to be set. The files there are almost certainly configured to use 2.5.8, as far as I can work out.
So my question is: how is the wrapper choosing to use 2.5.4 and where am I going the find these Groovy language files?
Also, presumably the version in the dependency section of build.gradle applies only to my testing and building files (i.e. written by me in Groovy), and has nothing to do with Gradle's own build actions and other tasks?
NB I'm tempted to uninstall my system Gradle and my system Groovy, since they just confuse the issue, and just rely on using the wrapper. Is this a sensible idea?
Gradle comes bundled with Groovy and does not look at what other versions you have installed on your system. This is why you are seeing different Groovy versions across different Gradle versions. You cannot change this version as it is part of Gradle and likely won't work with any other versions. If you are curious, you can look in the "lib" folder in your Gradle distribution to see all third-party libraries to Gradle, including Groovy - just don't go fiddling around with them.
As you mention, having declared a compile dependency to Groovy in your build script makes that particular version used when compiling. This is generally the only thing you should care about. (By the way, compile is deprecated, and you should use implementation.)
I am not sure what your goal is, but I would highly recommend only using the Gradle wrapper scripts, which means you can uninstall the system installation of Gradle if you like. You can ignore the Groovy version on your system (or uninstall it if you are not using it elsewhere).

which one is the latest version of maven to use

I am trying to use maven in our project and am new to it.
checking this https://maven.apache.org/download.cgi
3.6.0 version is latest version to download.
Someone was saying there is maven 4 is latest. Not sure where to download this from and can we use this for java 8.
Which one is latest version to use?
From https://maven.apache.org/download.cgi
Apache Maven 3.6.0 is the latest release and recommended version for
all users.
Works nicely with Java 8. Note that your IDE may bundle an older version in the unlikely case you run into problems.

How to stop gradle from downloading every time

I have installed gradle in Ubuntu 16.04.
Here is the output for gradle -v
------------------------------------------------------------
Gradle 2.10
------------------------------------------------------------
Build time: 2016-01-26 15:17:49 UTC
Build number: none
Revision: UNKNOWN
Groovy: 2.4.5
Ant: Apache Ant(TM) version 1.9.6 compiled on July 8 2015
JVM: 1.8.0_101 (Oracle Corporation 25.101-b13)
OS: Linux 4.4.0-38-generic amd64
But even now, whenever I create a new project based on gradle v2.10, it downloads it and then builds the project. According to the tutorials, after installing it, I shouldn't need to download it again. What is the problem here?
you will have to replace url with local path like this
distributionUrl = file\:///e:/android/gradle-2.10-bin.zip
and comment
distributionUrl=https\://services.gradle.org/distributions/gradle-2.10-all.zip
in gradle-wrapper.properties
I think you have two concepts mixed up:
A manual installation of gradle (gradle.bat / gradle.sh)
The gradle wrapper (gradlew.bat / gradlew.sh)
When you mention executing gradle -v this has absolutely no effect on the gradle wrapper. The wrapper works independently of any manually installed gradle versions.
Since you are referencing gradle being downloaded I assume you are discussing the gradle wrapper (gradlew). The wrapper will first check if it has downloaded the version previously by checking the cache stored under $GRADLE_USER_HOME so will only ever download each version once. Subsequent gradlew invocations will use the previously downloaded/unzipped installation.

Resources