About gradlew. I occasionally work with 3rd party stuff that is
incompatible with latest/greatest gradle. A few days ago, I split off a
few classes from a 20 year old project (ant based) into a lib and
decided to use gradle on one of my projects for the first time. (I
figure moving all my stuff
To have truly reproducible builds you need to have dependency
management for the tools and JDK, not just libraries. That's what the
wrapper is about. The wrapper can do hash checks on the downloaded Gradle
tool so it should be "safe". Using the Gradle mechanism to run with a
specified JDK, and f
On Sat, 6 Aug 2022 at 17:16, Bernd Michaely wrote:
>
> The original Gradle (7.5) doc says:
>
> The project root directory contains all source files that are part of your
> project. In addition, it contains files and directories that are generated by
> Gradle such as .gradle and build. While the
You're welcome :-)
On 07.08.22 03:08, Owen Thomas wrote:
Thanks Bernd for providing this important information. It is help like
this from you and others that helps me make sense of the complexity,
and I feel that I wouldn't be able to comprehend as quickly without
it. I hope that I might be a
FYI GitHub has a nice repository of gitignore files
https://github.com/github/gitignore/
(https://github.com/github/gitignore/tree/main)
Including for gradle
https://github.com/github/gitignore/blob/main/Gradle.gitignore
Eric Bresie
ebre...@gmail.com (mailto:ebre...@gmail.com)
> On August 6,
Well, really Gradle Wrapper is optional. It seems that the majority of
the users like that, so we do have Maven Wrapper as well now.
On 8/6/22 19:25, Andreas Reichel wrote:
Thank you for the response.
Looks like I don't need it because I never use Gradle Wrapper and
always stick with the late
Thank you for the response.
Looks like I don't need it because I never use Gradle Wrapper and
always stick with the latest Gradle Version only.
(I actually wished there was an option to avoid Gradle Wrapper
completely, there was never a Make or ANT wrapper for good. Downloading
random stuff from t
gradle/ folder (not the .gradle) usually the place to put additional
build logic, and if nothing else that's where Gradle places it's wrapper
gardle/wrapper/
Make sure you add the gardle/wrapper/gradle-wrapper.jar along with the
grade/wrapper/gradle-wrapper.properties file. (Unless some policy
Thanks Bernd for providing this important information. It is help like this
from you and others that helps me make sense of the complexity, and I feel
that I wouldn't be able to comprehend as quickly without it. I hope that I
might be able to provide others with the same from time to time.
On Sun,
The original Gradle (7.5) doc says:
The project root directory contains all source files that are part of
your project. In addition, it contains files and directories that are
generated by Gradle such as |.gradle| and |build|. While the former
are usually checked in to source control, the latt
I commit gradle folder (please note : not the .gradle folder) as it
contains the gradle wrapper which helps me restrict and use specific gradle
versions on my build systems.
I like this def provided by gitignore.io
https://www.toptal.com/developers/gitignore/api/gradle
*Cheers*
Mani/Naren/Iyer
*T
I've also ignored "./build" as keeping these files in version control is
silly.
Now that that's done, I can forget about it for another decade or so. :)
On Sat, 6 Aug 2022 at 11:36, Owen Thomas wrote:
> Sorry, I have misquoted the folder in the title. The folder I intended to
> quote is "./.gra
Sorry, I have misquoted the folder in the title. The folder I intended to
quote is "./.gradle/nb-cache", and I have corrected the title of this email
accordingly.
What I will do then is ignore ".gradle" from each project's base directory.
Let me know if that is not correct or is incomplete.
Thank
On Fri, 2022-08-05 at 17:52 -0700, Laszlo Kishalmi wrote:
> while gradle/ folders
> shall be committed
Laszlo,
thank you for advise, please care to elaborate. Why should it be there
when it can be rebuild on demand? What is the advantage of tracking it
and the disadvantage of dismissing it?
S
,gradle/ folders should be on the ignore list, while gradle/ folders
shall be committed
On 8/5/22 17:26, Owen Thomas wrote:
I have my projects running. All is good in the world.
I see the directory indicated in the title of this message sometimes
contains files for projects with old names (I
Owen,
not sure what best practise is, but I exclude ALL gradle folder and
files except the Build (build.gradle) file, From that, gradle can
always sort out itself and nothing else is needed.
Cheers
Andreas
On Sat, 2022-08-06 at 10:26 +1000, Owen Thomas wrote:
> I have my projects running. All i
I have my projects running. All is good in the world.
I see the directory indicated in the title of this message sometimes
contains files for projects with old names (I converted my project names
from camel to kebab case when this was indicated to me as the standard in
gradle/maven, so I did as I
17 matches
Mail list logo
