I've finally been able to nail down one of those pesky unexpected
exceptions in NetBeans' Java source handling (NPE at
ElementHandle.resolve()) and to make it reproducible in a sample
project, see https://issues.apache.org/jira/browse/NETBEANS-3191. This
was in 11.1, but it is reproducible in
On Thu 2018-04-05 at 16:03h, Leo Donahue wrote on netcat:
> Thanks for clarification on the cached credentials.
>
> Test case #1 file in Project 1 is locked.
> Test case #4 file with same name like in previous, file with same name like
> in previous, file with same name like in previous - is the
On Thu 2018-04-05 at 12:44h, Leo Donahue wrote on netcat:
> Thank you Niklas,
>
> >> SVN does not store the username in the working copy
> http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html
>
> The svn redbook seems misleading.
> "The fact that the *svn info* command, which does
Sorry for the late reply...
On Thu 2018-03-29 at 20:21h, Leo Donahue wrote on netcat:
:
> Steps from Test case 12. Conflict resolved are confusing - I can't tell
> which project of the three now in project explorer I'm supposed to select
> project root on.
In test suite 3, test case 12, you can
This is part of the sample project's configuration.
See ${nb-install}/java/modules/org-netbeans-modules-java-examples.jar
-> org/netbeans/modules/java/examples/anagrams.zip
-> nbproject/project.properties:
javac.source=1.6
javac.target=1.6
"New project" just creates a copy of the sample project,
Thanks. Just to clarify, this means that SnvKit won't be available for NetBeans
9 unless someone turns it into a third-party plugin?
Niklas
On Tue 2018-03-20 at 13:48h, Glenn Holmer wrote on netcat:
> On 03/20/2018 01:19 PM, Niklas Matthies wrote:
> > For SVN testing, w
For SVN testing, we noticed that the SvnKit implementation is not available in
the current NetBeans builds (only JavaHL and CLI), so we can't test it. I found
https://issues.apache.org/jira/browse/NETBEANS-86 which might be related and
commented there, but maybe someone here knows what is up
