You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Laszlo Kishalmi <la...@gmail.com> on 2020/07/09 22:14:24 UTC

Apache NetBeans 12.0-u1is available for testing.

Dear all,

This is a call for a test round on the upcoming NetBeans 12.0-u1 
release. This update one is also serve to test the requires effort to 
bring such updates in the future.

The PR-s in this release can be found at:

https://github.com/apache/netbeans/milestone/7?closed=1

In order to test the update please add the following update center to a 
12.0 NetBeans installation:

https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/35/artifact/dist/netbeans/nbms/updates.xml.gz

If everything goes well, and nobody complains, I'm moving forward with 
these binaries and source making it officially available for vote on 
Sunday (12th of July, 2020) evening PST.

We are going to vote on the whole source this time. However no 
installers, nor convenience zip distribution would be provided. The 
updates will be distributed using our 12.0 release update center.

--

   Laszlo Kishalmi


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Maven versioning and updates for 12.0u1 was: Apache NetBeans 12.0-u1is available for testing.

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 22 Jul 2020 at 17:20, Jesse Glick <ty...@gmail.com> wrote:
> This is the most natural approach I think, though you may also need to
> amend Maven version numbers to mention more detailed information in
> case there is some possibility of multiple uploads being performed
> with slightly different sources but the same OIDE-M-S-V.

That should not happen.  It would be a failure in our current release
processes, although I'm not sure we have any way to definitively catch
it?  The failure to upload to Maven in that case would be good though.

> > It is however likely to be incompatible with the current tooling support in the IDE
>
> Which tooling support? I regularly use Maven BOMs from projects open
> in NetBeans and it works fine.

maven-apisupport I assume.  I think that's what Eric raised when I
suggested a BOM approach to this.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Maven versioning and updates for 12.0u1 was: Apache NetBeans 12.0-u1is available for testing.

Posted by Jesse Glick <ty...@gmail.com>.
On Fri, Jul 17, 2020 at 8:06 AM Jaroslav Tulach
<ja...@gmail.com> wrote:
> Using "OpenIDE-Module-Specification-Version" primarily and group the
> release artifacts by one or more BOMs is an interesting idea.

This is the most natural approach I think, though you may also need to
amend Maven version numbers to mention more detailed information in
case there is some possibility of multiple uploads being performed
with slightly different sources but the same OIDE-M-S-V. My
suggestion:

https://github.com/stapler/netbeans-stapler-plugin/blob/8765695ae5180c64a6006af718edcc4fe9b9b87a/pom.xml#L79-L108

> It is however likely to be incompatible with the current tooling support in the IDE

Which tooling support? I regularly use Maven BOMs from projects open
in NetBeans and it works fine.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Maven versioning and updates for 12.0u1 was: Apache NetBeans 12.0-u1is available for testing.

Posted by Jaroslav Tulach <ja...@gmail.com>.
Thank you Neil and Eric,
for your considerations. It is great to hear that there can be Maven
artifacts for 12.0u1!

For the 12.0u1 I would choose the simplest solution: e.g. release
everything as RELEASE120u1

Once I wrote an essay (but I cannot find it anymore) why to use per release
versioning (e.g. everything as RELEASExy in our case) and why to use
individual per module versions. It all depends whether you want to simplify
"use" or "re-use". Do you expect that people are going to consume the whole
set of JAR files at once (that is a "use") or will they pick individual
modules up as cherries (that's "re-use")? The NetBeans module runtime
versioning prefers "re-use", while the Maven packaging simplifies "use".

I can imagine we could have both. E.g. upload each module under RELEASExy
as well as its real "OpenIDE-Module-Specification-Version". Then updates
could just upload new "OpenIDE-Module-Specification-Version" JARs as our
NBMs do. Such system would remain compatible and it would increase
flexibility for those who only need to pick few bugfixes up there and there.

Using "OpenIDE-Module-Specification-Version" primarily and group the
release artifacts by one or more BOMs is an interesting idea. That would
probably balance "use" and "re-use" quite fine. It is however likely to be
incompatible with the current tooling support in the IDE - e.g. we have to
expect things will be broken for a while.

Thanks for thinking about the Maven artifact packaging!
-jt

po 13. 7. 2020 v 15:02 odesílatel Neil C Smith <ne...@apache.org>
napsal:

> On Mon, 13 Jul 2020 at 13:38, Eric Barboni <sk...@apache.org> wrote:
> > Bom pom with dependencymanagement section would be an addition to
> clusters.
> > Clusters have actual dependencies in them.
>
> Yes, I know.  I had a look at the Maven build system after we talked
> about it a little while ago, and realised that it would have to be
> separate to the cluster files.  Although the cluster files could
> depend on the BOM for versions too?
>
> I guess this is a topic that deserves a different thread, though -
> might be difficult to achieve in an update.
>
> I plan to get my head a little better around the Maven process during
> 12.1 - expect some questions! ;-)
>
> Thanks and best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 13 Jul 2020 at 13:38, Eric Barboni <sk...@apache.org> wrote:
> Bom pom with dependencymanagement section would be an addition to clusters.
> Clusters have actual dependencies in them.

Yes, I know.  I had a look at the Maven build system after we talked
about it a little while ago, and realised that it would have to be
separate to the cluster files.  Although the cluster files could
depend on the BOM for versions too?

I guess this is a topic that deserves a different thread, though -
might be difficult to achieve in an update.

I plan to get my head a little better around the Maven process during
12.1 - expect some questions! ;-)

Thanks and best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: Apache NetBeans 12.0-u1is available for testing.

Posted by Eric Barboni <sk...@apache.org>.
Bom pom with dependencymanagement section would be an addition to clusters. 
Clusters have actual dependencies in them.

So we may have regeneration of clusters and bom per release and update with "human understandable" name. We need a way to prevent regenerating existing version specification. 

Start to make sense :D

Eric

-----Message d'origine-----
De : Neil C Smith <ne...@apache.org> 
Envoyé : lundi 13 juillet 2020 12:05
À : dev <de...@netbeans.apache.org>
Objet : Re: Apache NetBeans 12.0-u1is available for testing.

On Mon, 13 Jul 2020 at 10:52, Eric Barboni <sk...@apache.org> wrote:
> I'm not sure to understand what is the BOM approach,
...
>  Upgrading with spec version,
>         you have to look each entry, map the spec version to the 
> release you want. (IDE tool needed) maven version plugin can help 
> getting only last version. (20 changes to do)

Exactly, the BOMs could be like current cluster files, but with modules under dependency management rather than dependencies (eg. as in https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html)
 That way you'd have one or more BOM for version RELEASE-120-1 with all the modules and their spec versions in it, and the correct versions would be picked up everywhere used.  But it will likely need some UI changes in the IDE.

The BOM would be the mapping you're talking about between platform version and spec version?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 13 Jul 2020 at 10:52, Eric Barboni <sk...@apache.org> wrote:
> I'm not sure to understand what is the BOM approach,
...
>  Upgrading with spec version,
>         you have to look each entry, map the spec version to the release you want. (IDE tool needed) maven version plugin can help getting only last version. (20 changes to do)

Exactly, the BOMs could be like current cluster files, but with
modules under dependency management rather than dependencies (eg. as
in https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html)
 That way you'd have one or more BOM for version RELEASE-120-1 with
all the modules and their spec versions in it, and the correct
versions would be picked up everywhere used.  But it will likely need
some UI changes in the IDE.

The BOM would be the mapping you're talking about between platform
version and spec version?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: Apache NetBeans 12.0-u1is available for testing.

Posted by Eric Barboni <sk...@apache.org>.
I'm not sure to understand what is the BOM approach,

Doing the release of maven artifact the current way is just the easy way, it cost only a bit of time to upload and sign

AFAIK,  the plugin that populate is able to release per spec version. (Need to be rechecked maybe). So maven side could be done. Unsure how external will be versioned.

If we want to go to another system we will have more work to do in the IDE.

Issue 1,
Apache NetBeans IDE list platform according to maven version name RELEASE* of a specific artefact. RELEASE120 or RELEASE120-1 is understandable by user in the selection panel. 

But changing to spec version,  will present specification version and we will need a mechanism for a mapping that for example
  o.n.core version 3.57 is platform 12.0
  o.n.core version 3.58 is platform 12.1

If update are created 12.0-u1 and nothing is changed on core,  user will have to clue that there is a 12.0-u1.
So all in one, we  need a more complex mechanism to get the mapping  information.

Issue 2,
 upgrade existing maven project to a specific release, or last release. As an example, let's have a plugin with 20 artifacts of Apache NetBeans used
 Upgrading a maven project in the current approach, 
	is only to rename all RELEASEoldversion entry to RELEASEversionyouwant or a property to change (bulk change, 1 search and replace), 
 	maybe check that module became api or vice versa
 Upgrading with spec version,
	you have to look each entry, map the spec version to the release you want. (IDE tool needed) maven version plugin can help getting only last version. (20 changes to do) 


No easy to do,
Best Regards
Eric


-----Message d'origine-----
De : Neil C Smith <ne...@apache.org> 
Envoyé : lundi 13 juillet 2020 10:40
À : dev <de...@netbeans.apache.org>
Objet : Re: Apache NetBeans 12.0-u1is available for testing.

On Mon, 13 Jul 2020 at 09:14, Eric Barboni <sk...@apache.org> wrote:
> It's possible to get the maven bits alongside a patch release, we only 
> need a version scheme like RELEASE120-u1 knowing that RELEASE120-1 is  
> taken by eventually a republish  (may happen in the future)
>
> https://github.com/apache/netbeans-jenkins-lib/edit/master/meta/netbeansrelease.json mavenversion for release120 need to be updated for version number RELEASE120-u1 and it should be ok to stage.

It would be great to look at a BOM approach to this for the future, with the modules by spec version.  Having to update every Maven module for each update release doesn't seem sustainable if we start having more of them.  And be good if the implementation versions remained in sync with the UCs?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 13 Jul 2020 at 09:14, Eric Barboni <sk...@apache.org> wrote:
> It's possible to get the maven bits alongside a patch release, we only need a version scheme like RELEASE120-u1 knowing that RELEASE120-1 is  taken by eventually a republish  (may happen in the future)
>
> https://github.com/apache/netbeans-jenkins-lib/edit/master/meta/netbeansrelease.json mavenversion for release120 need to be updated for version number RELEASE120-u1 and it should be ok to stage.

It would be great to look at a BOM approach to this for the future,
with the modules by spec version.  Having to update every Maven module
for each update release doesn't seem sustainable if we start having
more of them.  And be good if the implementation versions remained in
sync with the UCs?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: Apache NetBeans 12.0-u1is available for testing.

Posted by Eric Barboni <sk...@apache.org>.
Hi Jaroslav,

It's possible to get the maven bits alongside a patch release, we only need a version scheme like RELEASE120-u1 knowing that RELEASE120-1 is  taken by eventually a republish  (may happen in the future)

https://github.com/apache/netbeans-jenkins-lib/edit/master/meta/netbeansrelease.json mavenversion for release120 need to be updated for version number RELEASE120-u1 and it should be ok to stage.

Best Regards
Eric

 
-----Message d'origine-----
De : Jaroslav Tulach <ja...@gmail.com> 
Envoyé : lundi 13 juillet 2020 06:04
À : Apache NetBeans <de...@netbeans.apache.org>
Cc : Laszlo Kishalmi <la...@gmail.com>
Objet : Re: Apache NetBeans 12.0-u1is available for testing.

- pátek 10. července 2020 0:14:24 CEST, Laszlo Kishalmi -
> We are going to vote on the whole source this time. 

OK.

> However no
> installers, nor convenience zip distribution would be provided. 

OK.

> The
> updates will be distributed using our 12.0 release update center.

I am in need of updated Maven artifacts as my projects (for example Bck2Brwsr) depend on the bugfixes available only in 12.0u1.

-jt



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Jaroslav Tulach <ja...@gmail.com>.
- pátek 10. července 2020 0:14:24 CEST, Laszlo Kishalmi -
> We are going to vote on the whole source this time. 

OK.

> However no
> installers, nor convenience zip distribution would be provided. 

OK.

> The
> updates will be distributed using our 12.0 release update center.

I am in need of updated Maven artifacts as my projects (for example Bck2Brwsr) depend 
on the bugfixes available only in 12.0u1.

-jt


Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Mark Eggers <it...@yahoo.com.INVALID>.
OK,

So I tried the following:

1. uninstall previous version of SilkSVN javahl libraries
2. installed SilkSVN javahl libraries - 1.12.0 64 bit
3. Tools->Options->Team->Versioning->Subversion
a. set client to JavaHL
b. set path to the SilkSVN javahl libraries

When I apply (press the apply button), the client reverts back to CLI.

The command line integration works fine, albeit really slowly with
TortoiseSVN.

I'll try backing up my user directories, and starting fresh.

I've carried things along from 8.2->11.1->12.0, so maybe it's time to do
a fresh launch.

Mark
/mde/

On 7/9/2020 5:57 PM, Laszlo Kishalmi wrote:
> We have upgraded the JNA version in 11.2, so I do not think that this
> would be an issue raised by the patches included in 12.0-u1
> 
> Unfortunately due to licensing reasons SvnKIT is not supported any more
> in the mainline NetBeans 9ans afaik nobody took care to support it as
> third party) you can still make svn work using the native java library
> bindings coming with subversion (you might need to install those
> separately). That's the fastest Subversion integration, BTW.
> 
> On 7/9/20 3:36 PM, Mark Eggers wrote:
>> I just loaded this, and am working with subversion in NetBeans 12.
>>
>> Some plugins require plugin JNA to be installed.
>> The plugin JNA is requested in version >= 1.11 (release version 1) but
>> only 2.3 (of release version different from 1) was found.  The following
>> plugin is affected:       Subversion SvnKit Client Library
>>
>> Mark
>> /mde/
>>
>> On 7/9/2020 3:14 PM, Laszlo Kishalmi wrote:
>>> Dear all,
>>>
>>> This is a call for a test round on the upcoming NetBeans 12.0-u1
>>> release. This update one is also serve to test the requires effort to
>>> bring such updates in the future.
>>>
>>> The PR-s in this release can be found at:
>>>
>>> https://github.com/apache/netbeans/milestone/7?closed=1
>>>
>>> In order to test the update please add the following update center to a
>>> 12.0 NetBeans installation:
>>>
>>> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/35/artifact/dist/netbeans/nbms/updates.xml.gz
>>>
>>>
>>>
>>> If everything goes well, and nobody complains, I'm moving forward with
>>> these binaries and source making it officially available for vote on
>>> Sunday (12th of July, 2020) evening PST.
>>>
>>> We are going to vote on the whole source this time. However no
>>> installers, nor convenience zip distribution would be provided. The
>>> updates will be distributed using our 12.0 release update center.
>>>
>>> -- 
>>>
>>>    Laszlo Kishalmi
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Laszlo Kishalmi <la...@gmail.com>.
We have upgraded the JNA version in 11.2, so I do not think that this 
would be an issue raised by the patches included in 12.0-u1

Unfortunately due to licensing reasons SvnKIT is not supported any more 
in the mainline NetBeans 9ans afaik nobody took care to support it as 
third party) you can still make svn work using the native java library 
bindings coming with subversion (you might need to install those 
separately). That's the fastest Subversion integration, BTW.

On 7/9/20 3:36 PM, Mark Eggers wrote:
> I just loaded this, and am working with subversion in NetBeans 12.
>
> Some plugins require plugin JNA to be installed.
> The plugin JNA is requested in version >= 1.11 (release version 1) but
> only 2.3 (of release version different from 1) was found.  The following
> plugin is affected:       Subversion SvnKit Client Library
>
> Mark
> /mde/
>
> On 7/9/2020 3:14 PM, Laszlo Kishalmi wrote:
>> Dear all,
>>
>> This is a call for a test round on the upcoming NetBeans 12.0-u1
>> release. This update one is also serve to test the requires effort to
>> bring such updates in the future.
>>
>> The PR-s in this release can be found at:
>>
>> https://github.com/apache/netbeans/milestone/7?closed=1
>>
>> In order to test the update please add the following update center to a
>> 12.0 NetBeans installation:
>>
>> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/35/artifact/dist/netbeans/nbms/updates.xml.gz
>>
>>
>> If everything goes well, and nobody complains, I'm moving forward with
>> these binaries and source making it officially available for vote on
>> Sunday (12th of July, 2020) evening PST.
>>
>> We are going to vote on the whole source this time. However no
>> installers, nor convenience zip distribution would be provided. The
>> updates will be distributed using our 12.0 release update center.
>>
>> -- 
>>
>>    Laszlo Kishalmi
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Mark Eggers <it...@yahoo.com.INVALID>.
Thanks!

This happily works. I'm guessing that this is not a long term solution,
though.

Hopefully I'll get people to move to git sooner or later.

Thanks again!

Mark
/mde/

On 7/10/2020 1:57 PM, Matthias Bläsing wrote:
> Hi,
> 
> the module is still present, but not part of the regular build anymore
> (aren't licenses great :-)). See if this build helps:
> 
> https://www.doppel-helix.eu/org-netbeans-libs-svnClientAdapter-svnkit.nbm
> 
> Greetings
> 
> Matthias
> 
> Am Donnerstag, den 09.07.2020, 15:36 -0700 schrieb Mark Eggers:
>> I just loaded this, and am working with subversion in NetBeans 12.
>>
>> Some plugins require plugin JNA to be installed.
>> The plugin JNA is requested in version >= 1.11 (release version 1)
>> but
>> only 2.3 (of release version different from 1) was found.  The
>> following
>> plugin is affected:       Subversion SvnKit Client Library
>>
>> Mark
>> /mde/
>>
>> On 7/9/2020 3:14 PM, Laszlo Kishalmi wrote:
>>> Dear all,
>>>
>>> This is a call for a test round on the upcoming NetBeans 12.0-u1
>>> release. This update one is also serve to test the requires effort
>>> to
>>> bring such updates in the future.
>>>
>>> The PR-s in this release can be found at:
>>>
>>> https://github.com/apache/netbeans/milestone/7?closed=1
>>>
>>> In order to test the update please add the following update center
>>> to a
>>> 12.0 NetBeans installation:
>>>
>>> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/35/artifact/dist/netbeans/nbms/updates.xml.gz
>>>
>>>
>>> If everything goes well, and nobody complains, I'm moving forward
>>> with
>>> these binaries and source making it officially available for vote
>>> on
>>> Sunday (12th of July, 2020) evening PST.
>>>
>>> We are going to vote on the whole source this time. However no
>>> installers, nor convenience zip distribution would be provided. The
>>> updates will be distributed using our 12.0 release update center.
>>>
>>> -- 
>>>
>>>   Laszlo Kishalmi
>>>
>>>
>>> -----------------------------------------------------------------
>>> ----
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,

the module is still present, but not part of the regular build anymore
(aren't licenses great :-)). See if this build helps:

https://www.doppel-helix.eu/org-netbeans-libs-svnClientAdapter-svnkit.nbm

Greetings

Matthias

Am Donnerstag, den 09.07.2020, 15:36 -0700 schrieb Mark Eggers:
> I just loaded this, and am working with subversion in NetBeans 12.
> 
> Some plugins require plugin JNA to be installed.
> The plugin JNA is requested in version >= 1.11 (release version 1)
> but
> only 2.3 (of release version different from 1) was found.  The
> following
> plugin is affected:       Subversion SvnKit Client Library
> 
> Mark
> /mde/
> 
> On 7/9/2020 3:14 PM, Laszlo Kishalmi wrote:
> > Dear all,
> > 
> > This is a call for a test round on the upcoming NetBeans 12.0-u1
> > release. This update one is also serve to test the requires effort
> > to
> > bring such updates in the future.
> > 
> > The PR-s in this release can be found at:
> > 
> > https://github.com/apache/netbeans/milestone/7?closed=1
> > 
> > In order to test the update please add the following update center
> > to a
> > 12.0 NetBeans installation:
> > 
> > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/35/artifact/dist/netbeans/nbms/updates.xml.gz
> > 
> > 
> > If everything goes well, and nobody complains, I'm moving forward
> > with
> > these binaries and source making it officially available for vote
> > on
> > Sunday (12th of July, 2020) evening PST.
> > 
> > We are going to vote on the whole source this time. However no
> > installers, nor convenience zip distribution would be provided. The
> > updates will be distributed using our 12.0 release update center.
> > 
> > -- 
> > 
> >   Laszlo Kishalmi
> > 
> > 
> > -----------------------------------------------------------------
> > ----
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> > 
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > 
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Apache NetBeans 12.0-u1is available for testing.

Posted by Mark Eggers <it...@yahoo.com.INVALID>.
I just loaded this, and am working with subversion in NetBeans 12.

Some plugins require plugin JNA to be installed.
The plugin JNA is requested in version >= 1.11 (release version 1) but
only 2.3 (of release version different from 1) was found.  The following
plugin is affected:       Subversion SvnKit Client Library

Mark
/mde/

On 7/9/2020 3:14 PM, Laszlo Kishalmi wrote:
> Dear all,
> 
> This is a call for a test round on the upcoming NetBeans 12.0-u1
> release. This update one is also serve to test the requires effort to
> bring such updates in the future.
> 
> The PR-s in this release can be found at:
> 
> https://github.com/apache/netbeans/milestone/7?closed=1
> 
> In order to test the update please add the following update center to a
> 12.0 NetBeans installation:
> 
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/35/artifact/dist/netbeans/nbms/updates.xml.gz
> 
> 
> If everything goes well, and nobody complains, I'm moving forward with
> these binaries and source making it officially available for vote on
> Sunday (12th of July, 2020) evening PST.
> 
> We are going to vote on the whole source this time. However no
> installers, nor convenience zip distribution would be provided. The
> updates will be distributed using our 12.0 release update center.
> 
> -- 
> 
>   Laszlo Kishalmi
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists