- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 36 for gradleWrapper (0.3 sec)
-
platforms/documentation/docs/src/docs/userguide/running-builds/introduction/command_line_interface_basics.adoc
[[command_line_interface_basics]] = Command-Line Interface Basics The command-line interface is the primary **method of interacting with Gradle** outside the IDE. image::gradle-basic-2.png[] Use of the <<gradle_wrapper.adoc#gradle_wrapper_reference, Gradle Wrapper>> is highly encouraged. Substitute `./gradlew` (in macOS / Linux) or `gradlew.bat` (in Windows) for `gradle` in the following examples.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 2.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/directory_layout.adoc
<4> Contains the JAR file and configuration of the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>>. <5> Project-specific <<build_environment.adoc#sec:gradle_configuration_properties,Gradle configuration properties>>. <6> Scripts for executing builds using the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>>.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Apr 24 23:00:38 UTC 2024 - 13K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/userguide_single.adoc
include::github-actions.adoc[leveloffset=+2] include::travis-ci.adoc[leveloffset=+2] [[part:reference]] == **REFERENCE** include::command_line_interface.adoc[leveloffset=+2] include::gradle_wrapper.adoc[leveloffset=+2] include::plugin_reference.adoc[leveloffset=2] include::third_party_integration.adoc[leveloffset=2] == GRADLE DSLs and API include::groovy_build_script_primer.adoc[leveloffset=+2]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Mar 14 22:56:31 UTC 2024 - 8.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/reference/ci-systems/travis-ci.adoc
[listing.terminal.sample-command] ---- $ ./gradlew build BUILD SUCCESSFUL 14 actionable tasks: 14 executed ---- The project provides the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>> as part of the repository. It is a recommended practice for any Gradle project as it enables your project to built on CI without having to install the Gradle runtime.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 5.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/other/init_scripts.adoc
+ This lets you package a custom Gradle distribution containing custom build logic and plugins. You can combine this with the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle wrapper>> to make custom logic available to all builds in your enterprise. If more than one init script is found, they will all be executed in the order specified above.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 05:36:09 UTC 2024 - 8.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/reference/ci-systems/jenkins.adoc
[listing.terminal.sample-command] ---- $ ./gradlew build BUILD SUCCESSFUL 14 actionable tasks: 14 executed ---- The project provides the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>> as part of the repository. It is a recommended practice for any Gradle project as it enables your project to built on CI without having to install the Gradle runtime.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 6.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/reference/third_party_integration.adoc
* <<teamcity.adoc#build_teamcity,TeamCity>> * <<travis-ci.adoc#build_travis,Travis CI>> Even if you don't use one of the above, you can almost certainly configure your CI platform to use the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>> scripts. == How to integrate with Gradle There are two main ways to integrate a tool with Gradle: * The Gradle build uses the tool
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 8.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/best-practices/organizing_gradle_projects.adoc
The initialization scripts come bundled with the distribution and are applied every time the build is run. Developers only need to point their checked-in <<gradle_wrapper.adoc#gradle_wrapper_reference,Wrapper>> files to the URL of the custom Gradle distribution.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 08:16:36 UTC 2024 - 13.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/reference/ci-systems/teamcity.adoc
[listing.terminal.sample-command] ---- $ ./gradlew build BUILD SUCCESSFUL 14 actionable tasks: 14 executed ---- The project provides the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>> as part of the repository. It is a recommended practice for any Gradle project as it enables your project to built on CI without having to install the Gradle runtime.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 8.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/troubleshooting.adoc
If you followed the <<installation.adoc#installation,installation instructions>>, and aren’t able to execute your Gradle build, here are some tips that may help. If you installed Gradle outside of just invoking the <<gradle_wrapper.adoc#gradle_wrapper_reference,Gradle Wrapper>>, you can check your Gradle installation by running `gradle --version` in a terminal. You should see something like this: ---- ❯ gradle --version
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Apr 06 02:22:03 UTC 2024 - 11.5K bytes - Viewed (0)