[NETBEANS-3025] Netbeans editor looses dependent gradle module if the name of its jar changes frequently

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Information Provided
• Affects Version/s: 11.1
• Component/s: projects - Gradle
• Assignee: Laszlo Kishalmi
• Reporter: Adam Walczak
• Created: 25/Aug/19 13:37
• Updated: 03/Nov/20 15:47
• Resolved: 25/Aug/19 16:32

Description

Lets say I have the following multi module project:

 

build.gralde

def projectVersion = new Date().format("yyyy-MM-dd-HH-mm")
subprojects {
    apply plugin: 'java'
    
    sourceCompatibility = 11
    group = 'foo'
    version = projectVersion
}

foo-commons/build.gradle

// nothing

foo-app/build.gradle

dependencies {
    compile project(":foo-commons")
}

This will cause Netbeas to often looses sight of the foo-commons library code and classes from there will be not found when editing source code in foo-app. The project will however  build without any problem in gradle.

 

I think Netbeans has a problem with the fact that the name of the library jar build from foo-commons changes every time any thing changes in that code as the projects version is part of the name (foo-commons-2019-08-12-15-54.jar)

 

A workaround to make Netbean never loose sight of the dependancy is to make its jar name constant like so:

 

foo-commons/build.gradle

jar.archiveName = 'foo-commons.jar'