Maven profiles equivalent of Gradle

Mehmet Catalbas :

I'm trying to achieve a simple scenario in my spring boot project build: including / excluding dependencies and packaging war or jar depending on the environment.

So for example, for the environment dev include devtools and package jar, for prod package war etc.

I know it is not XML based configuration anymore and I can basically write if statements in my build.gradle but is there a recommended way of achieving this?

Can I declare some common dependencies and refer them in a single file instead of creating multiple build files?

Is there a best practice changing build configuration based on the build target environment?

lance-java :

ext {
    devDependencies = ['org.foo:dep1:1.0', 'org.foo:dep2:1.0']
    prodDependencies = ['org.foo:dep3:1.0', 'org.foo:dep4:1.0']
    isProd = System.properties['env'] == 'prod'
    isDev = System.properties['env'] == 'dev'
}

apply plugin: 'java'

dependencies {
    compile 'org.foo:common:1.0'
    if (isProd) {
       compile prodDependencies
    }
    if (isDev) {
       compile devDependencies
    }
}

if (isDev) tasks.withType(War).all { it.enabled = false }

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=448223&siteId=1

Maven profiles equivalent of Gradle

Maven package phase equivalent in Gradle

todo ---- maven profiles usage

Detailed profiles maven

2, Maven profiles and configuration

maven pom profiles

Maven equivalent in .NET C#

Detailed explanation of the use of profiles in maven

Is there a Java/Maven equivalent of package.jsons "bin"?

maven package different profiles depending on the environment

Maven profiles multi-environment configuration

Maven profiles multi-environment configuration

Maven's profiles function introduction, maven custom plug-in plugin

Comparison of gradle and maven

Gradle project to Maven project

maven project to gradle project

ant、maven、gradle

Multi-environment portable builds using maven profiles

Maven-based profiles multi-environment configuration

maven project active: @profiles.active@error reporting, idea tool

With Gradle, will you still choose Maven?

Gradle modifies the Maven repository address

gradle uses maven repository settings

maven stone using multi-module maven profiles specified in several specific sub-modules build a project in

The basic steps to use the npm package management tool are equivalent to the front-end Maven

Excited: springboot gave up maven, chose gradle, gradle built springboot

Gradle 7.0+ releases Gradle plugin to private maven repository Notes

[Turn] use maven of resources, filter and profile to achieve different environments using different profiles

Maven configuration, dependent on third-party jar package packaged multi-environment configuration and Profiles

WEB project profiles idea2019 created by Maven to be unified on the form here