On Wed, 2022-08-03 at 22:54 -0700, László Kishalmi wrote:
> Compile was discouraged at 3.4, marked for deprecation in 4.0 they
> removed it in 7.0. that's pretty long time. 4 years.
Apologies when digressing too far: 4 years looks pretty long, although
there are still tons of documentation and
Compile was discouraged at 3.4, marked for deprecation in 4.0 they removed
it in 7.0. that's pretty long time. 4 years.
On Wed, Aug 3, 2022, 20:51 Owen Thomas wrote:
>
>
> On Thu, 4 Aug 2022 at 12:37, Andreas Reichel <
> andr...@manticore-projects.com> wrote:
>
>> Just be prepared. Its still
On Thu, 4 Aug 2022 at 12:37, Andreas Reichel
wrote:
> Just be prepared. Its still very much worth it in my opinion.
>
Thanks Andreas. Yea, even though, if I were Gradle, I might have kept the
"compile" option for a while longer, I think backwards compatibility might
be a little overrated too.
Owens,
On Thu, 2022-08-04 at 12:29 +1000, Owen Thomas wrote:
> I observe that Gradle isn't fussed about backwards compatibility as
> much as Java.
you are spot on. While I love Gradle, I found that features change
faster than documentation and examples can keep up.
You will find lots of outdated
Indeed Eric. Thankfully, I found the answer and the remainder of the
conversion to Gradle went reasonably smoothly over source code which
currently calls nothing but Java SE currently. That might now change
without too much added complication.
I observe that Gradle isn't fussed about backwards
Think there have been some changes in Gradle around compile and implementation
(1). May depend on what version of Gradle is in use as well.
Eric Bresie
ebre...@gmail.com (mailto:ebre...@gmail.com)
(1) https://tomgregory.com/gradle-implementation-vs-compile-dependencies/
> On August 2, 2022 at
