This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git
The following commit(s) were added to refs/heads/trunk by this push:
new 1eb5a52af4 Improved: Replace SvnCheckout in Gradle (OFBIZ-12868
1eb5a52af4 is described below
commit 1eb5a52af41d096e56eb4671922075a01041515e
Author: Jacques Le Roux <jacques.le.r...@les7arts.com>
AuthorDate: Mon Jan 1 18:02:06 2024 +0100
Improved: Replace SvnCheckout in Gradle (OFBIZ-12868
Comments out the pullPluginSource and pullAllPluginsSource Gradle tasks and
updates the documentation to use the pullPluginSource and
pullAllPluginsSource
OS scripts
---
README.adoc | 23 ++++++++++++-----------
build.gradle | 4 ++--
2 files changed, 14 insertions(+), 13 deletions(-)
diff --git a/README.adoc b/README.adoc
index 5d25221fed..4d5996c211 100644
--- a/README.adoc
+++ b/README.adoc
@@ -692,24 +692,25 @@ If you need username and password to access the custom
repository:
[[pull-an-official-plugin-from-source-control]]
=== Pull an official plugin from source control
-Download an official plugin from source control (currently subversion) and
place
-it in the plugins directory. In addition, this task also executes the "install"
-task if it is defined for the plugin being downloaded.
+Download an official plugin from source control and place it in the plugins
directory.
+It's able to handle branches switches
-This task is mostly useful when working on the trunk branch as it pulls in the
-latest version of a plugin.
-
-`gradlew pullPluginSource -PpluginId=ecommerce`
+MS Windows: `pullPluginSource example` +
+Unix-like OS: `./pullPluginSource.sh example`
[[pull-all-official-plugins-from-source-control]]
=== Pull all official plugins from source control
Download all officially supported plugins from source control (currently
git) and place them in /plugins.
+It's able to handle branches switches
+
WARNING! This task deletes the /plugins directory and replaces it with the
official plugins.
-`gradlew pullAllPluginsSource`
+MS Windows: `pullAllPluginsSource` +
+Unix-like OS: `./pullAllPluginsSource.sh`
+
This task makes it easy to download and develop officially supported plugins.
It
is mostly used by developers or individuals working on the trunk branch. We do
@@ -809,9 +810,9 @@ as a replacement for both "special-purpose" and
"hot-deploy".
If you need to load the components in the plugins directory in a specific order
place a component-load.xml file in the plugins directory listing the order.
-To check out a plugin from source control use the *pullPluginSource* Gradle
-task. To check out all plugins from source control use the
-*pullAllPluginsSource*. *Beware* this deletes a previously existing plugins
+To check out a plugin from source control use the Windows or Unix-like
*pullPluginSource* script.
+To check out all plugins from source control use the
+*pullAllPluginsSource* script. *Beware* this deletes a previously existing
plugins
directory.
[[running-gradle-tasks-without-an-internet-connection]]
diff --git a/build.gradle b/build.gradle
index ddce209416..7c0866217f 100644
--- a/build.gradle
+++ b/build.gradle
@@ -980,7 +980,7 @@ task pullPlugin(group: ofbizPlugin, description: 'Download
and install a plugin
}
}
}
-
+/* The pullPluginSource and pullPluginSource task are now replaced by the OS
scripts pullPluginSource and pullAllPluginsSource
task pullPluginSource(group: ofbizPlugin, description: 'Download and install a
plugin from source control') {
if (project.hasProperty('pluginId')) {
@@ -1033,7 +1033,7 @@ task pullAllPluginsSource(group: ofbizPlugin,
doLast {
gradlewSubprocess(['installAllPlugins'])
}
-}
+}*/
// ========== Clean up tasks ==========
task cleanCatalina(group: cleanupGroup, description: 'Clean Catalina data in
runtime/catalina/work') {
