Gradle equivalent of below maven dependencies share please

<build>
		<finalName>CLASSamFileImport</finalName>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>3.8.1</version>
	
				<configuration>
					<source>1.8</source>
					<target>1.8</target>
					<encoding>UTF-8</encoding>
					<compileArgument>-Xlint:all</compileArgument>
					<showWarnings>true</showWarnings>
					<showDeprecation>true</showDeprecation>
				</configuration>	
						
			</plugin>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-jar-plugin</artifactId>
				<configuration>
					<archive>
						<manifest>
							<mainClass>com.wf.fileimport.batch.common.FileImportTemplateProcess</mainClass>
							<packageName>com.wf.fileimport.batch.common</packageName>
						</manifest>
					</archive>
				</configuration>
			</plugin>
			<plugin>
				<artifactId>maven-assembly-plugin</artifactId>
				<executions>
					<execution>
						<phase>package</phase>
							<goals>
								<goal>attached</goal>
							</goals>
					</execution>
				</executions>
				<configuration>
					<descriptorRefs>
						<descriptorRef>jar-with-dependencies</descriptorRef>
					</descriptorRefs>
					<archive>
						<manifest>
							<mainClass>com.wf.fileimport.batch.common.FileImportTemplateProcess</mainClass>
						</manifest>
					</archive>
				</configuration>
			</plugin>
		</plugins>		
	</build>

What exactly are you asking?
That someone here rewrites your Maven build as Gradle build?
That will most probably not happen unless you find someone you can pay for it. :slight_smile:
If you just want to know which Gradle plugins to use instead of those Maven plugins:

maven-compiler-plugin => java or java-library depending on whether it is a library or not, with the JVM toolchains feature for the Java 8 configuration, not setting the compatibilities

maven-jar-plugin => java or java-library depending on whether it is a library or not

maven-assembly-plugin with attached goal in the lifecycle is even discouraged in Maven documentation, but => com.github.johnrengelman.shadow, but I personally highly recommend not to use such bad practice fat jars, they just make more issues than they are worth and they do not really provide any added value. See https://fatjar.net/ for some quotes about it. Better use the application plugin to build a proper application distribution, or if it really must be a fat jar, at least build a good-practice one like it is done with Spring Boot jars.

1 Like