[nbusers] Bug with Compile-On-Save with Maven?

  • From: Jeff < >
  • To:
  • Subject: [nbusers] Bug with Compile-On-Save with Maven?
  • Date: Fri, 31 Aug 2012 16:30:48 -0600

There seems to be a bug with the compile-on-save feature in NB 7.2 (may have existed in earlier versions).

I use Maven profiles to set system properties to determine the environment configuration files I need to load.  If I have the compile-on-save feature enabled, a new environment seems to be created that does not contain the same system properties nor classpath/ClassLoader set.  

This causes my System.getProperties() calls to return NULL.

This also causes ClassLoader.getSystemResourceAsStream(...) calls to not find anything I need suggesting either the classpath is not set or it is running with a different ClassLoader.

Is this a feature/known side-effect of the compile-on-save feature?

I ♥ DropBox !! 

[nbusers] Bug with Compile-On-Save with Maven?

Jeff 08/31/2012

Project Features

About this Project

www was started in November 2009, is owned by jpirek, and has 25 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20150226.965aeb8). © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
Please Confirm