I just read an ASF members thread about this article:
https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
One member mentioned that the Groovy project is using the Gradle's dependency
verification feature[1] in the Apache Groovy build.
I suggest we do the same, even after the move from JCenter to MavenCentral where
things should be safer.
[1] https://docs.gradle.org/current/userguide/dependency_verification.html
This commit includes:
The verification-metadata.xml and verification-keyring.gpg used by the
verification task
*.gpg as binary in .gitattrubtes for verification-keyring.gpg
The documentation about the verification in sy-dependency-verification.adoc
with a link and some unrelated changes in security.adoc about security for
OFBiz in production
An empty line removed in build.gradle
As reported by Ethan Vos on user ML, sometimes the alias between wget and
Invoke-WebRequest is not present on Windows 7, better keep it simple!
Also removes the comment:
Anyway I believe this should be only used in dev environment
which is no longer true
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1867998 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-10145)
When you run 'sh gradle/init-gradle-wrapper.sh', if the script gradlew at the OFBiz root isn't present we download it from bintray.
Improvements to comments and messages in the init-gradle-wrapper.sh script do on r1865605 by Jacopo
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1866120 13f79535-47bb-0310-9956-ffa450edef68
to our build notes
(OFBIZ-10145)
Adds the Windows init-gradle-wrapper scripts (both .bat et .ps1) in all
concerned branch (trunk, R18, R17)
These are very simple because I believe (almost?) nobody is using a Windows
server to deploy OFBiz in production. So they will be only used in development
environment. In case deployment in production is needed they supply a base to
work on...
The init-gradle-wrapper.ps1 scripts use only HTTP and not HTTPS because it's
very difficult to handle all the issues related with different versions of
Powershell and .net in different versions of Windows. Better to let that to
deployment in case it's really needed...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1864927 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-11133)
As discussed OFBIZ-11133, reverts r1862326.
Actually only puts back the wrapper files in gradle/wrapper directory
I used
gradlew wrapper --gradle-version=5.0 --distribution-type=bin
to regenerate the version.
Only gradle-wrapper.properties was correctly regenerated, gradle-wrapper.jar was
still the 5.5 version (weird but true).
So I copied gradle-wrapper.jar 5.0 version from
tools\Buildbot\Gradle\Wrapper\R18.12
There were no changes in gradlew scripts
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1862747 13f79535-47bb-0310-9956-ffa450edef68
our build notes
(OFBIZ-10145)
As discussed in dev ML and OFBIZ-11133, reverts all commits done for OFBIZ-10145:
r1862356, r1862354, r1862353, r1861783, r1861766
But keeps in README.doc the added line in r1861766:
==== Clean system and load the complete OFBiz data
I'm uncertain about what will happen with the gradle/wrapper directory and the
wrapper version there (currently 5.5 and in between these commits).
But anyway not a big deal to get it back
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1862745 13f79535-47bb-0310-9956-ffa450edef68
our build notes
(OFBIZ-10145)
Applies the last waiting gradlew.bat.patch in OFBIZ-10145
Fixes a trivial issue in Mathieu last commits: repeated "-Xms64m" in gradlew
scripts.
Uses HTTP in init-gradle-wrapper.ps1 instead of HTTP. Not everyone has an HTTPS
access to the tools repo.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1862353 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-11131)
The upgrade has been done with the following command:
$ ./gradlew wrapper --gradle-version=5.5 --distribution-type=bin
Our “gradlew” scripts modification has been preserved and
“gradle/init-gradle-wrapper.sh” has been updated to download the new
version of the wrapper jar.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1862326 13f79535-47bb-0310-9956-ffa450edef68
provided by user
(OFBIZ-11124)
In framework/webtools XML Data Export I reported an issue, Jayansh fixed it:
If user provided file name and output directory in that case the entity xml
files are generated at both locations, i.e. at root we have test.xml and in user
provided output directory we have multiple files with [entityname].xml.
The expected change would be if user provided both output directory and filename
then file should be created in given directory with given filename.
Thanks: Jayansh Shinde for the fix
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1862045 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-10145) (LEGAL-288)
As regards to LEGAL-288 [1] we remove the gradle-wrapper.jar from the source and future release packages.
Now when you run ./gradlew (or gradlew), we check before that gradle/wrapper/gradle-wrapper.jar is present
otherwise we download it before calling the wrapper.
To realize the download, we need as a prerequisite to have:
Unix-like: curl or wget
MS windows: wget
If any issue appears, it's possible to set gradle-wrapper.jar and gradle-wrapper.properties by hand on the directory gradle/wrapper/
Thanks to Jacques Leroux and Swapnil M Mane for their help
[1] https://issues.apache.org/jira/browse/LEGAL-288
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1861766 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-9972)
After finally resolving the issue with gradle not accepting spaces in task
names, we are able to smoothly upgrade to gradle version 5.
This has reference to the discussion thread: https://s.apache.org/vQgW
Thanks: Mathieu Lirzin for feedback and test patch.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1848062 13f79535-47bb-0310-9956-ffa450edef68
This commit represents a pivotal change in the history of the
project in which the build system is being replaced from Apache
Ant to Gradle of which the discussion mail thread link is below.
Thanks to everyone who helped with testing and feedback
This commit delivers the following:
- add the gradle wrapper directory in gradle/* which holds
all items necessary for gradle to run
- add the build.gradle master script
- add the settings.gradle script which declares all the subprojects
- add documentation for how to use everything in a new file called
README.md (written in markdown)
The new script is capable of the functionality that used to exist
in Ant with some additional features including automation of eclipse
files generation and many other functions.
To complete this new feature, we need to apply the following _after_
this commit:
- change the buildbot to utilize gradle instead of ant
- delete all ant & maven scripts
- replace all local jars with remote ones from jcenter
Reference thread: http://ofbiz.markmail.org/message/vstt3wxuubmjgmqj?q=Important+Changes+to+Trunk+and+Use+of+Ant+%26+Gradle
Reference JIRA: https://issues.apache.org/jira/browse/OFBIZ-7534
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1751309 13f79535-47bb-0310-9956-ffa450edef68