Geschrieben von everflux am März 11th, 2015
I you are using Netbeans to develop a maven based (multi-module) (web) application you may have encountered this problem: The resources are not copied when re-running the application. The easy option: Build the project always before running it.
This is slow and just feels wrong. Netbeans lets you customize the life-cycle of your project, so you can hook all maven executions you like, especially the ‚resources‘ build step.
Open project properties, select ‚Actions‘ and add ‚resources:resources‘ to the front of the ‚execute Goals‘ field:
You can add your own custom action as well, in case you want to trigger a specific step independently of the overall project lifecycle, for example the ‚resources:resources‘ goal:
Geschrieben von everflux am März 7th, 2015
As I regularly test different versions of Netbeans as part of the community acceptance program (NetCAT) and for my own fun and benefit I sometimes struggle to start of the right version: Usually the release version is the right one to go. During NetCAT the beta version needs to be tested and when new features are so promising that you want to run the nightly, you go with that.
I came up with a simple solution to never launch the wrong edition: Differently colored Netbeans icons. This is how my Gnome launcher looks:
Easy to tell that red is the nightly, without looking at the icon text! If you want that for yourself, you can get the icons here:
The icons are created using Gimp and just rotating the colors, so it’s a little hacky but does the trick.
In Gnome you can use the application ‚alacarte‘ (or ‚main menu‘ if you run the english locale) to customize your launchers. Just change the icon:
Neue Kommentare