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 having. The
solutions in IntelliJ I have read so far involve fiddling in an obscure
corner of the projects' settings, and they have not resolved my problem
either.
As I demonstrated, the problem appears to be with my Gradle project. I'm
using the CLI to issue commands to Gradle. The build is failing there, and
the solution to fix it seems to reside with telling Gradle what it wants to
hear.
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.
Owen.
On Tue, 2 Aug 2022 at 13:04, Andreas Reichel <andr...@manticore-projects.com>
wrote:
> 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 came to.
>
> On Tue, 2022-08-02 at 12:59 +1000, Owen Thomas wrote:
>
> 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 directory has the following:
>
> rootProject.name = 'CliqueSpace'
>
> include ':Concept'
> include ':PeerDevice'
>
> There are other includes in the above file, but I don't think it is
> necessary to quote them here.
>
> In the Concept directory (CliqueSpace/Concept), build.gradle contains the
> following:
>
> description = 'Concept'
>
> In the PeerDevice directory (CliqueSpace/PeerDevice), build.gradle
> contains the following:
>
> description = 'PeerDevice'
>
> dependencies {
> compile project(':Concept')
> }
>
> At the moment, I only feel confident using gradle from the CLI. So, when I
> open a CLI window within the CliqueSpace directory, and run "gradle project
> PeerDevice", I get the following:
>
> owen@owen-Latitude-5511:~/Development/CliqueSpace/Code/trunk/CliqueSpace$
> gradle project PeerDevice
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file
> '/home/owen/Development/CliqueSpace/Code/trunk/CliqueSpace/PeerDevice/build.gradle'
> line: 4
>
> * What went wrong:
> A problem occurred evaluating project ':PeerDevice'.
> > Could not find method compile() for arguments [project ':Concept'] on
> object of type
> org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> BUILD FAILED in 493ms
>
> In short, having followed the instructions from a few different sources
> now, I don't know what I'm doing wrong. It might be good for the reader to
> know that Concept/src/main/java has source code in it that compiles, but
> PeerDevice/src/main/java also has source code where almost every Java
> module has broken out in a rash of unresolved dependencies.
>
> Thanks for any help,
>
> Owen.
>
>
>
