Adam Walczak created NETBEANS-3025:
--------------------------------------
Summary: Netbeans editor looses dependent gradle module if the
name of its jar changes frequently
Key: NETBEANS-3025
URL: https://issues.apache.org/jira/browse/NETBEANS-3025
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 11.1
Reporter: Adam Walczak
Assignee: Laszlo Kishalmi
Lets say I have the following multi module project:
build.gralde
{code:java}
def projectVersion = new Date().format("yyyy-MM-dd-HH-mm")
subprojects {
apply plugin: 'java'
sourceCompatibility = 11
group = 'foo'
version = projectVersion
}
{code}
foo-commons/build.gradle
{code:java}
apply plugin: 'java'
{code}
foo-app/build.gradle
{code:java}
dependencies {
compile project(":foo-commons")
}
{code}
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
{code:java}
apply plugin: 'java'
jar.archiveName = 'foo-commons.jar'
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
