RE: MissingResourceException

2020-01-15 Thread Eirik Bakke
om: Neil C Smith Sent: Wednesday, January 15, 2020 12:36 PM To: Eirik Bakke Cc: Marco Rossi ; List NetBeans Mailing ; Oliver Rettig Subject: Re: MissingResourceException On Wed, 15 Jan 2020 at 17:17, Eirik Bakke wrote: > Though you're on ant, and I'm using Maven (and the bugzilla bug above

Re: MissingResourceException

2020-01-15 Thread Emilian Bold
> There was an old bug about this on > https://bz.apache.org/netbeans/show_bug.cgi?id=221781 . Maybe we should > create a corresponding new JIRA issue. [Note: How cool the old bugzilla was migrated to Apache!] > Well, related. My first thought on this was Compile on Save. I don't > think

Re: MissingResourceException

2020-01-15 Thread Neil C Smith
On Wed, 15 Jan 2020 at 17:17, Eirik Bakke wrote: > Though you're on ant, and I'm using Maven (and the bugzilla bug above refers > to Maven). Maybe they are two different bugs. Well, related. My first thought on this was Compile on Save. I don't think I've got that enabled in a single project

Re: MissingResourceException

2020-01-15 Thread Marco Rossi
Yes, it is a new ant based project. I can confirm that a clean build fixes the problem, until any changes on the the panel form will be performed. And this is very annoying, especially at first when I have to design my forms. In the meantime I could follow the Eirik suggestion and move away

Re: MissingResourceException

2020-01-14 Thread Oliver Rettig
Hi Marco, sometimes I get also the "MissingResource" exceptions for @Message annotations in bigger ant based platform apps. I cauld resolve this by invocing clean-build by hand for single modules. The difficulty was to find out the sequence of modules I have to do this. This was difficult

RE: MissingResourceException

2020-01-14 Thread Eirik Bakke
Is this an ant or maven-based project? Does doing a clean build fix the problem? (When working with NetBeans platform applications, I find that many annotation changes will require a complete clean build of the entire project. For this reason I will probably move away from @Message