Svatopluk Dedic created NETBEANS-5623:
-----------------------------------------
Summary: 'fallback' project without trust can turn to 'evaluated'
Key: NETBEANS-5623
URL: https://issues.apache.org/jira/browse/NETBEANS-5623
Project: NetBeans
Issue Type: Improvement
Components: projects - Gradle
Reporter: Svatopluk Dedic
Assignee: Laszlo Kishalmi
During prototyping, I've encountered a strange thing:
{code:java}
NbGradleProjectImpl prjImpl =
prj.getLookup().lookup(NbGradleProjectImpl.class);
assertTrue(prjImpl.getGradleProject().getQuality().worseThan(NbGradleProject.Quality.EVALUATED));
// attempt to load everything
prjImpl.setAimedQuality(NbGradleProject.Quality.FULL);
// ... it loaded, but did not escalate the quality bcs not trusted
assertTrue(prjImpl.getGradleProject().getQuality().worseThan(NbGradleProject.Quality.EVALUATED));
{code}
I expected (the assert at the end) that a fallback project won't change as it's
not permitted to execute gradle for it. But it turned to evaluated (no gradle
was executed, in fact).
I consider that a bug - is it ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
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
