Re: Gradle won't resolve dependency: what's wrong here?

> On Aug 4, 2022, at 7:37 AM, Owen Thomas wrote: > > On Thu, 4 Aug 2022 at 15:54, 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 > > No problem. I'll just

Re: Re: Gradle won't resolve dependency: what's wrong here?

On Thu, 4 Aug 2022 at 15:54, 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 > No problem. I'll just have to be mindful of this when following advice from people about Gradle. Thanks all. Until

Re: Re: Gradle won't resolve dependency: what's wrong here?

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

Re: Re: Gradle won't resolve dependency: what's wrong here?

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

Re: Re: Gradle won't resolve dependency: what's wrong here?

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.

Re: Re: Gradle won't resolve dependency: what's wrong here?

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

Re: Re: Gradle won't resolve dependency: what's wrong here?

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

Re: Re: Gradle won't resolve dependency: what's wrong here?

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

Re: Gradle won't resolve dependency: what's wrong here?

And restarting NetBeans (after rebooting my laptop) seems to have cleared the PeerDevice project of its rash. Now to include the remainder of the projects... On Tue, 2 Aug 2022 at 16:23, Owen Thomas wrote: > Hey Laszlo. > > Sorry for not doing as you have asked, but while you were probably >

Re: Gradle won't resolve dependency: what's wrong here?

Hey Laszlo. Sorry for not doing as you have asked, but while you were probably composing your message, my Gradle project built! I don't know if that means that I'm good - (it usually doesn't) I need to add a lot more subprojects to the root project - but all I did was to change

Re: Gradle won't resolve dependency: what's wrong here?

Well, I've done and see a few dozen of Gradle builds, though this sounds alien to me. If you could share your project structure (main folders and their build.gradle files, maybe we can help sort this thing out. On 8/1/22 22:39, Owen Thomas wrote: While I've been doing other things, I have come

Re: Gradle won't resolve dependency: what's wrong here?

While I've been doing other things, I have come to the conclusion that I need something, possibly in my build.gradle file of the Concept project, that refers to the Groovy method "compile". Perhaps I will need to start here. On Tue, 2 Aug 2022 at 14:02, Jason Abreu wrote: > When I converted

Re: Gradle won't resolve dependency: what's wrong here?

When I converted about 30 projects from Any to Gradle, including multiple multi-project builds, I noticed a few peculiar things. Firstly, NetBeans gets a background task hung up every now and then. The only solution for this was to exit NetBeans then find the hung up task and kill it. Once

Re: Gradle won't resolve dependency: what's wrong here?

Hi Owen. On Tue, 2022-08-02 at 13:46 +1000, Owen Thomas wrote: > Thanks again Andreas; I hope someone can tell me what Gradle wants to > hear. If perhaps you can help me show me how to get my projects to > work in IntelliJ, then I would indeed be most thankful. Can you share you Gradle file with

Re: Gradle won't resolve dependency: what's wrong here?

Hi Andreas. In some way, I agree with you: NetBeans could make the conversion process easier. Although I have only been trying to move my Ant projects to Gradle now for probably little more than a day, I have also tried to use IntelliJ, and their advice seems unable to solve the problem that I am

Re: Gradle won't resolve dependency: what's wrong here?

Owen, I have had the same problem and found only IntelliJ supporting Gradle Multi Projects properly. It made me switch. @Netbeans: I am really sorry to write that. I have used and loved Netbeans for my entire life. But not liking Maven (not at all!) and unable to stick with Ant, this is what it

Gradle won't resolve dependency: what's wrong here?

Hello again. I am perplexed at the following problem. I have a multi-project build in a directory named "CliqueSpace". It's build.gradle file has the following: subprojects { apply plugin: 'java' repositories { mavenCentral() } } The settings.gradle file or the same