On 2020-12-21 16:40, Thomas Kellerer wrote:
Alan schrieb am 21.12.2020 um 20:58:
More confusing and more than a bit of a pain. At the risk of being
repetitive, does anyone know how to persist window layouts and open
files across version updates? Even a clue would help.
I typically just keep t
Alan schrieb am 21.12.2020 um 20:58:
More confusing and more than a bit of a pain. At the risk of being
repetitive, does anyone know how to persist window layouts and open
files across version updates? Even a clue would help.
I typically just keep the old user dir. I only delete the "var/cach
I did find the cause of the problem. And it was a Netbeans fault. :(
For some unknown reasons, when Netbeans generated that test file
instead of import of org.junit.jupiter.api.Test it placed import of
org.junit.Test
Therefore, Jupiter engine did not recognized the @Test annotation.
I did delete a
Also you can go with the Snap package, which will be auto upgrade
whenever the new version is out. When that come out the new version will
report on startup if you would like to import the previous workspace
which is usually safe. If I'll have some time, I'd experiment with Snaps
auto directory
I did try it. I also did upgrade Junit from v.4.11 to v.4.13.1 and
org.junit.jupiter from 5.6.0 to 5.7.0.
Result was the same.
Gary Greenberg
Staff Software Engineer
Data Product Development, BI-A
E: ggree...@visa.com
M: 650-269-7902
[EmailSig-TaglineVersion]
From: Jose Ch
Sent: Sunday, Decemb
More confusing and more than a bit of a pain. At the risk of being
repetitive, does anyone know how to persist window layouts and open
files across version updates? Even a clue would help.
Although I'm sure it's idiosyncratic, I've got a really specific setup
typically with 50-100 open files a
Hi Andreas,
I said before, that if I am running in general, this particular test is skipped.
If I try to run 'Test File' action, it fails not in the test itself, but in
maven before test is launched.
I did run maven with -e flag and got the following stack trace:
Failed to execute goal
org.apac
On Mon, 21 Dec 2020 at 18:47, Scott Palmer wrote:
> I think a better option would be to have a button to upgrade to a new release
> when one is available.
Definitely a message or button here would be good, and needs to be LTS aware ...
There is already a notification for new releases - "just" n
It is possible, however the project view will not show your C++ source files.
For that you have to use the Files view.
I would love to see better integration for Gradle-based C++ projects as I often
work on projects with a JNI component.
Also the Gradle native builds work with the Visual C++
And it has always caused this confusion...
We should at least add a message in the update UI to tell users to do a manual
download and install to move to a new release.
I think a better option would be to have a button to upgrade to a new release
when one is available.
It should also be explic
> Well since unfortunately the encoding of a property file is set as ISO-8859-1
> in it spec,
At least for JDK 11 the API says the opposite :
https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/PropertyResourceBundle.html,
see the API paragraph.
And indeed it's what I experime
Well since unfortunately the encoding of a property file is set as
ISO-8859-1 in it spec, I'd use a generator step in the build which would
translate the UTF-8 characters into \u of the final Bundle.properties.
On 12/21/20 6:56 AM, Jerome Lelasseux wrote:
I use the crowdin.com platform (fre
I use the crowdin.com platform (free for open-source!) to get the translations
done for my Netbeans RCP application. It gets synchronized automatically to
GitHub nicely.
The problem is that I pull UFT-8 encoded Bundle*.properties, and the RCP
platform expects ISO-8859-1 encoding, so special ch
NetBeans Platform RELEASE90 application (developed under Apache NetBeans
12.1 under linux):
When I create application package with myapp - Properties - Build -
Installer
the contained (in ZIP-file) /etc/myapp.conf file contains weird default
directories:
default_userdir="${DEFAULT_USERDIR_ROOT}/d
Thanks Boris. Yes this is what I've started to do using the branding
localization. I don't reuse many Netbeans menu items, so it should be ok.
The problem I have now is how to deal with the ISO-8859-1 encoding required for
Bundle*.properties, because I use Crowdin and it generates UTF-8 files...
http://wiki.netbeans.org/DevFaqInvokeActionProgrammatically
To find the action id behind a menu item, you can open layer.xml/ from your project (if you don't have a layer.xml yet, just create on).
Then browse to Menu/View/Show Only Editor, then righ-click "Go to declaration":
To run something upo
On Mon, 21 Dec 2020 at 12:51, Oliver Rettig wrote:
> It is only a warning that the file maybe is too big. There are lots of
> configuration possibilities available for experiences users.
There is already
https://bits.netbeans.org/12.2/javadoc/properties.html although this
is not listed there tha
I am developing a netbeans RELEASE90 platform based application.
all gui is placed in editor area.
Is there a way to programmatically call "Show Only Editor" (like in the
"view"-menu)
on startup of application?
Hi,
It is only a warning that the file maybe is too big. There are lots of
configuration possibilities
available for experiences users.
Maybe a central page in the wiki which collects all the settings/properties
would be fine.
Is there such a collection somewhere? Where can it place in the
It has always been a requirement to install NetBeans from scratch when you
want to use a new release.
Gj
On Mon, 21 Dec 2020 at 13:30, Marco Ambu wrote:
> Thanks, is that because of the way I installed netbeans or any other
> reason like linux or the Check for updates feature is not working and
Thanks, is that because of the way I installed netbeans or any other reason
like linux or the Check for updates feature is not working and not meant
to? In that case is it going to be removed?
On Mon, 21 Dec 2020 at 11:53, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Yes, you ne
Yes, you need to reinstall whenever a new release is released.
Gj
On Mon, Dec 21, 2020 at 10:41 AM Marco Ambu wrote:
> Hi,
>
> I installed netbeans 12.1 in linux (don't remember if I used the zip file
> or the shell installer).
> Anyway I see 12.2 is available but running "Check for updates" i
Hi,
I know there is support for gradle (although I have never used it) and
there is support for C++ using makefiles.
Does anyone know if it is possible to use gradle to build C++ projects in
netbeans?
Thanks,
Marco
Hi,
I installed netbeans 12.1 in linux (don't remember if I used the zip file
or the shell installer).
Anyway I see 12.2 is available but running "Check for updates" in my
Netbeans says that there are no updates available.
Is that supposed to work or do we need to re-install it every time a new
r
I think the software program sucks if the software did not advise user in
the error message to adjust the parameter.
J-Dorg.openide.text.big.file.size=10.
On Mon, 21 Dec 2020, 08:34 Oliver Rettig, wrote:
> Hi all,
>
>
>
> Neil is completely right - thanks for the hint.
>
>
>
> The warni
Hi all,
Neil is completely right - thanks for the hint.
The warning is opened if a configurable maximum file size is reached. The
default value for
this is 1MB and can be increased by by adding system property, e.g.
-J-Dorg.openide.text.big.file.size=10
I will think about to use this mechanis
26 matches
Mail list logo
