You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@netbeans.apache.org by * William <wi...@gmail.com> on 2018/10/06 07:54:28 UTC
Fwd: SVN fix?
Hi again list,
Yes may be Netbeans 10 will sort it out. From the previous discussion of
this point (circa 2018-08-20):
Actually, you need no workaround. The bug NETBEANS-771 was fixed. See
https://github.com/apache/incubator-netbeans/tree/master/subversion.
I build the module from source and installed the new module version. I
don't know if there is a automatic update and how this is handled right
now. But I didn't get any updates up to now.
found by searching "users@netbeans.apache.org svn" on the list
So it works for people who rebuild Netbeans and there was no update to
"see". That's fine.
This however doesn't explain lack of JavaHL support and absentce of the
SvnKit. Under Netbeans 9.0, with both Java 10 and Java 8 this happens when
you click "Load next 30 days":
[image: image.png]
While yu can clickon JavaHL client, requires a restart. Once restarted,
there is No Change. Both Java 8 and Java 10.
One can easily see that SvnKit is no longer in the drop-down list.
Pop-up below appears. Every time, no matter what svn.exe CLI client is
specified.
[image: image.png]
Looking forward to Netbeans 10.
kind regards,
aplatypus.
On Wed, 26 Sep 2018 at 22:01, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
>
>
> On Wed, Sep 26, 2018 at 1:45 PM, * William <wi...@gmail.com>
> wrote:
>
>> Hmm
>>
>> This matter was discussed a month or more back. There appears to be NO
>> "SvbKit" and the 'JavaHL' reverts back to command line.
>>
>> On the command line, the version is:
>>
>> svn, version 1.8.16 (r1740329)
>> compiled May 5 2016, 17:51:02 on x86_64-unknown-linux-gnu
>>
>> Because the SVN functionality is not happening, new files, moves and
>> renames get lost and miss being committed.
>>
>> This happens on Linux and Windows. On the Windows box, it is TortiseSVN
>> client. Netbeans v8.x al work as well as ever. Not certain on the
>> TortiseSVN client version. Again though, works with 8.2
>>
>> Personally I call this a regression error. No matter how it is
>> classified Netbeans 9 can't be used for production without an external SVN
>> client.
>>
>
>
> Well, just in this mail thread you can see that others do not have this
> problem -- e.g.., "Hmm, I don't have any problems with SVN with NetBeans
> 9," says Thomas Kellerer, above.
>
> Maybe a difference in your environment between 8.2 and 9 is that you're
> using a different JDK, for example, which could have some influence in some
> way? Are there other differences between the two environments?
>
> Next week, we should have a new release, for Apache NetBeans 10, you could
> try that and see if it resolves your problem
>
Re: SVN fix?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
You're welcome to join the NetCAT program and try out the latest release of
Apache NetBeans 10 and provide feedback:
https://cwiki.apache.org/confluence/display/NETBEANS/NetCAT+10.0+Participants
Gj
On Mon, Oct 8, 2018 at 8:33 AM Andreas Hauffe <an...@tu-dresden.de>
wrote:
> Hi,
>
> in my case (netbeans 9.0, java 1.8 or 10, OpenSUSE Leap 15.0 with svn libs
> 1.10) this is still a problem with the version. The svnkit is disable due
> to license problems. The javahl client of netbeans supports javahl libs up
> to version 1.9 and rejects the OS libs with version 1.10. The svn CLI
> client had the bug of parsing the version number. So if I install the svn
> module without the bug NETBEANS-771 only the CLI client will work and if I
> switch to javahl I'm getting the same behavior as discribed by aplatypus.
>
> --
> Regards,
> Andreas Hauffe
>
> Am 06.10.18 um 10:22 schrieb Geertjan Wielenga:
>
> The svnkit integration has been disabled, because some parts of it are
> under licenses that are not allowed in an ASF project.
>
> See: https://issues.apache.org/jira/browse/NETBEANS-1302
>
> Gj
>
>
> On Sat, Oct 6, 2018 at 9:54 AM * William <wi...@gmail.com>
> wrote:
>
>>
>> Hi again list,
>>
>> Yes may be Netbeans 10 will sort it out. From the previous discussion of
>> this point (circa 2018-08-20):
>>
>> Actually, you need no workaround. The bug NETBEANS-771 was fixed. See
>> https://github.com/apache/incubator-netbeans/tree/master/subversion.
>>
>> I build the module from source and installed the new module version. I
>> don't know if there is a automatic update and how this is handled right
>> now. But I didn't get any updates up to now.
>>
>> found by searching "users@netbeans.apache.org svn" on the list
>>
>> So it works for people who rebuild Netbeans and there was no update to
>> "see". That's fine.
>>
>> This however doesn't explain lack of JavaHL support and absentce of the
>> SvnKit. Under Netbeans 9.0, with both Java 10 and Java 8 this happens when
>> you click "Load next 30 days":
>>
>> [image: image.png]
>>
>> While yu can clickon JavaHL client, requires a restart. Once restarted,
>> there is No Change. Both Java 8 and Java 10.
>>
>> One can easily see that SvnKit is no longer in the drop-down list.
>>
>> Pop-up below appears. Every time, no matter what svn.exe CLI client is
>> specified.
>>
>> [image: image.png]
>>
>> Looking forward to Netbeans 10.
>>
>> kind regards,
>>
>> aplatypus.
>>
>> On Wed, 26 Sep 2018 at 22:01, Geertjan Wielenga <
>> geertjan.wielenga@googlemail.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 26, 2018 at 1:45 PM, * William <wi...@gmail.com>
>>> wrote:
>>>
>>>> Hmm
>>>>
>>>> This matter was discussed a month or more back. There appears to be
>>>> NO "SvbKit" and the 'JavaHL' reverts back to command line.
>>>>
>>>> On the command line, the version is:
>>>>
>>>> svn, version 1.8.16 (r1740329)
>>>> compiled May 5 2016, 17:51:02 on x86_64-unknown-linux-gnu
>>>>
>>>> Because the SVN functionality is not happening, new files, moves and
>>>> renames get lost and miss being committed.
>>>>
>>>> This happens on Linux and Windows. On the Windows box, it is
>>>> TortiseSVN client. Netbeans v8.x al work as well as ever. Not certain on
>>>> the TortiseSVN client version. Again though, works with 8.2
>>>>
>>>> Personally I call this a regression error. No matter how it is
>>>> classified Netbeans 9 can't be used for production without an external SVN
>>>> client.
>>>>
>>>
>>>
>>> Well, just in this mail thread you can see that others do not have this
>>> problem -- e.g.., "Hmm, I don't have any problems with SVN with
>>> NetBeans 9," says Thomas Kellerer, above.
>>>
>>> Maybe a difference in your environment between 8.2 and 9 is that you're
>>> using a different JDK, for example, which could have some influence in some
>>> way? Are there other differences between the two environments?
>>>
>>> Next week, we should have a new release, for Apache NetBeans 10, you
>>> could try that and see if it resolves your problem
>>>
>>
>>
Re: SVN fix?
Posted by Andreas Hauffe <an...@tu-dresden.de>.
Hi,
in my case (netbeans 9.0, java 1.8 or 10, OpenSUSE Leap 15.0 with svn
libs 1.10) this is still a problem with the version. The svnkit is
disable due to license problems. The javahl client of netbeans supports
javahl libs up to version 1.9 and rejects the OS libs with version 1.10.
The svn CLI client had the bug of parsing the version number. So if I
install the svn module without the bug NETBEANS-771 only the CLI client
will work and if I switch to javahl I'm getting the same behavior as
discribed by aplatypus.
--
Regards,
Andreas Hauffe
Am 06.10.18 um 10:22 schrieb Geertjan Wielenga:
> The svnkit integration has been disabled, because some parts of it are
> under licenses that are not allowed in an ASF project.
>
> See: https://issues.apache.org/jira/browse/NETBEANS-1302
>
> Gj
>
>
> On Sat, Oct 6, 2018 at 9:54 AM * William <william.full.moon@gmail.com
> <ma...@gmail.com>> wrote:
>
>
> Hi again list,
>
> Yes may be Netbeans 10 will sort it out. From the previous
> discussion of this point (circa 2018-08-20):
>
> Actually, you need no workaround. The bug NETBEANS-771 was fixed.
> See
> https://github.com/apache/incubator-netbeans/tree/master/subversion.
>
> I build the module from source and installed the new module
> version. I don't know if there is a automatic update and how this
> is handled right now. But I didn't get any updates up to now.
>
> found by searching "users@netbeans.apache.org
> <ma...@netbeans.apache.org> svn" on the list
>
> So it works for people who rebuild Netbeans and there was no
> update to "see". That's fine.
>
> This however doesn't explain lack of JavaHL support and absentce
> of the SvnKit. Under Netbeans 9.0, with both Java 10 and Java 8
> this happens when you click "Load next 30 days":
>
> image.png
>
> While yu can clickon JavaHL client, requires a restart. Once
> restarted, there is No Change. Both Java 8 and Java 10.
>
> One can easily see that SvnKit is no longer in the drop-down list.
>
> Pop-up below appears. Every time, no matter what svn.exe CLI
> client is specified.
>
> image.png
>
> Looking forward to Netbeans 10.
>
> kind regards,
>
> aplatypus.
>
> On Wed, 26 Sep 2018 at 22:01, Geertjan Wielenga
> <geertjan.wielenga@googlemail.com
> <ma...@googlemail.com>> wrote:
>
>
>
> On Wed, Sep 26, 2018 at 1:45 PM, * William
> <william.full.moon@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hmm
>
> This matter was discussed a month or more back. There
> appears to be NO "SvbKit" and the 'JavaHL' reverts back to
> command line.
>
> On the command line, the version is:
>
> svn, version 1.8.16 (r1740329)
> compiled May 5 2016, 17:51:02 on x86_64-unknown-linux-gnu
>
> Because the SVN functionality is not happening, new files,
> moves and renames get lost and miss being committed.
>
> This happens on Linux and Windows. On the Windows box, it
> is TortiseSVN client. Netbeans v8.x al work as well as
> ever. Not certain on the TortiseSVN client version.
> Again though, works with 8.2
>
> Personally I call this a regression error. No matter how
> it is classified Netbeans 9 can't be used for production
> without an external SVN client.
>
>
>
> Well, just in this mail thread you can see that others do not
> have this problem -- e.g.., "Hmm, I don't have any problems
> with SVN with NetBeans 9," says Thomas Kellerer, above.
>
> Maybe a difference in your environment between 8.2 and 9 is
> that you're using a different JDK, for example, which could
> have some influence in some way? Are there other differences
> between the two environments?
>
> Next week, we should have a new release, for Apache NetBeans
> 10, you could try that and see if it resolves your problem
>
>
Re: SVN fix?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
The svnkit integration has been disabled, because some parts of it are
under licenses that are not allowed in an ASF project.
See: https://issues.apache.org/jira/browse/NETBEANS-1302
Gj
On Sat, Oct 6, 2018 at 9:54 AM * William <wi...@gmail.com>
wrote:
>
> Hi again list,
>
> Yes may be Netbeans 10 will sort it out. From the previous discussion of
> this point (circa 2018-08-20):
>
> Actually, you need no workaround. The bug NETBEANS-771 was fixed. See
> https://github.com/apache/incubator-netbeans/tree/master/subversion.
>
> I build the module from source and installed the new module version. I
> don't know if there is a automatic update and how this is handled right
> now. But I didn't get any updates up to now.
>
> found by searching "users@netbeans.apache.org svn" on the list
>
> So it works for people who rebuild Netbeans and there was no update to
> "see". That's fine.
>
> This however doesn't explain lack of JavaHL support and absentce of the
> SvnKit. Under Netbeans 9.0, with both Java 10 and Java 8 this happens when
> you click "Load next 30 days":
>
> [image: image.png]
>
> While yu can clickon JavaHL client, requires a restart. Once restarted,
> there is No Change. Both Java 8 and Java 10.
>
> One can easily see that SvnKit is no longer in the drop-down list.
>
> Pop-up below appears. Every time, no matter what svn.exe CLI client is
> specified.
>
> [image: image.png]
>
> Looking forward to Netbeans 10.
>
> kind regards,
>
> aplatypus.
>
> On Wed, 26 Sep 2018 at 22:01, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>>
>>
>> On Wed, Sep 26, 2018 at 1:45 PM, * William <wi...@gmail.com>
>> wrote:
>>
>>> Hmm
>>>
>>> This matter was discussed a month or more back. There appears to be
>>> NO "SvbKit" and the 'JavaHL' reverts back to command line.
>>>
>>> On the command line, the version is:
>>>
>>> svn, version 1.8.16 (r1740329)
>>> compiled May 5 2016, 17:51:02 on x86_64-unknown-linux-gnu
>>>
>>> Because the SVN functionality is not happening, new files, moves and
>>> renames get lost and miss being committed.
>>>
>>> This happens on Linux and Windows. On the Windows box, it is TortiseSVN
>>> client. Netbeans v8.x al work as well as ever. Not certain on the
>>> TortiseSVN client version. Again though, works with 8.2
>>>
>>> Personally I call this a regression error. No matter how it is
>>> classified Netbeans 9 can't be used for production without an external SVN
>>> client.
>>>
>>
>>
>> Well, just in this mail thread you can see that others do not have this
>> problem -- e.g.., "Hmm, I don't have any problems with SVN with NetBeans
>> 9," says Thomas Kellerer, above.
>>
>> Maybe a difference in your environment between 8.2 and 9 is that you're
>> using a different JDK, for example, which could have some influence in some
>> way? Are there other differences between the two environments?
>>
>> Next week, we should have a new release, for Apache NetBeans 10, you
>> could try that and see if it resolves your problem
>>
>
>