Ready!
El 22/5/19 a las 22:38, Antonio escribió:
Thanks for reporting.
It seems the jenkins job responsible for generating Javadoc is not gone
https://builds.apache.org/job/netbeans-r110-apidocmaven/lastSuccessfulBuild/artifact/WEBZIP.zip
We'll try to restore it. Thanks for reporting!
Che
Thanks for reporting.
It seems the jenkins job responsible for generating Javadoc is not gone
https://builds.apache.org/job/netbeans-r110-apidocmaven/lastSuccessfulBuild/artifact/WEBZIP.zip
We'll try to restore it. Thanks for reporting!
Cheers,
Antonio
El 22/5/19 a las 20:39, Jerome Lelasseux
You can tell NetBeans to skip the tests on particular actions just to see
it build/compile cleanly.
Project -> Properties -> Actions -> Clean and Build project (for example)
then use the Add button to add Skip Tests.
Ultimately you'll want some tests and to resolve what's broken but my main
point
The Initializer suggestion was a great help. I still am having some issues
figuring out which classes are in which maven artifacts but
findjar was helpful and then I discovered "Add Dependency" in Netbeans. My
code is compiling ok but the build fails because I am
still having to track down things
Am I the only one to see Netbeans API websites down ? Below are the first
results when I google "netbeans API", which I've been doing for years without
any problem...
http://bits.netbeans.org/10.0/javadoc/ => "You don't have permission to
access /10.0/javadoc/on this server." (same if I rep
Ok, thanks.
Eduardo Quintanilla
Software Developer
From: Emilian Bold
Sent: miércoles, 22 de mayo de 2019 11:23 a. m.
To: Eduardo Quintanilla
Cc: users@netbeans.apache.org
Subject: Re: Netbeans 11 - Integrity of the release
That warning says there is no chain of trust to the key. But consideri
Theoretically it won't be that hard to implement at least the recognition of a
project with Kotlin DSL.
Just a hint for the implementation:
This is the file which is mainly respnsible to detect a Gradle project:
groovy/gradle/src/org/netbeans/modules/gradle/spi/GradleFiles.java
On 2019/05/16 15:
Unfortunately the Java modules are not supported yet. See:
https://issues.apache.org/jira/browse/NETBEANS-2004
It is on my list, it is not trivial though. I'm just clearing out my backlog
items and will work on it.
On 2019/05/21 14:11:30, "Terrell, Roger (CCI-Atlanta)"
wrote:
> Using NB 11,
That warning says there is no chain of trust to the key. But considering
you got the key from https://www.apache.org/dist/incubator/netbeans/KEYS
you can ignore that warning.
--emi
On Wed, May 22, 2019 at 5:23 PM Eduardo Quintanilla
wrote:
> Hi,
>
>
>
> I downloaded Netbeans 11[1] and got an e
Thanks, that was the problem. I overlooked that there is two signatures.
With the correct file:
gpg --import KEYS.txt
gpg --verify incubating-netbeans-11.0-bin.zip.asc
incubating-netbeans-11.0-bin.zip
The output now says:
gpg: Signature made 03/20/19 02:27:46 Central Standard Time (Mexico)
gpg
Hi,
I think you downloaded the *binary* and tried to verify it with a *key
for the source*.
Helmut
Am 22.05.2019 um 16:23 schrieb Eduardo Quintanilla:
>
> Hi,
>
>
>
> I downloaded Netbeans 11[1] and got an error when verifying the
> signature[3] of the downloaded zip.
>
> I got the KEYS from
Thanks, that was the problem.
The output now says:
gpg: Signature made 03/20/19 02:27:46 Central Standard Time (Mexico)
gpg:using RSA key 79C8F02A726E9EF53646D712B2BF814FA145CB2D
gpg: Good signature from "Laszlo Kishalmi (CODE SIGNING KEY)
" [unknown]
gpg: WARNING: This key is no
On Wed, 22 May 2019 at 15:23, Eduardo Quintanilla wrote:
> gpg --verify incubating-netbeans-11.0-source.zip.asc.txt
> incubating-netbeans-11.0-bin.zip
You appear to be verifying the source key against the binary zip?!
Best wishes,
Neil
-
Hi,
I downloaded Netbeans 11[1] and got an error when verifying the signature[3] of
the downloaded zip.
I got the KEYS from [2].
[1] -
https://us.mirrors.quenda.co/apache/incubator/netbeans/incubating-netbeans/incubating-11.0/incubating-netbeans-11.0-bin.zip
[2] - https://www.apache.org/dist/in
14 matches
Mail list logo
