This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Beans "autoloading" feature should be canceled (it installs automatically beans from jars just placed in "beans" directory). It does not seem to be used anyway, and it causes problems by mounting jars during startup (see issue 14258). We will rely on openide (projects) that the correct jars are always mounted. The preferred way of installing beans in jars is using xml layer by modules. According to this, Timer bean cannot be "autoloaded", but should installed through the xml layer too. I don't think it should be done in Form module. Timer is just an example bean, used by another examples which are already placed in usersguide module. So the Timer bean should be moved to usersguide module too. Together with the move, issue 13815 should be fixed (not to start the Timer in constructor; this requires also to modify ClockFrame example).
*** Issue 14258 has been marked as a duplicate of this issue. ***
*** Issue 13815 has been marked as a duplicate of this issue. ***
I'm ready to move the Timer bean to usersguide module. Do usersguide people agree with it (see the reasons above)? The move includes: - moving TimerBean.jar (appears in netbeans/beans dir), - moving sources (appears in netbeans/sources dir), - modifying layer.xml and UGModule.java, adding timerbean.xml - to mount TimerBean.jar automatically, - modifying layer.xml and Bundle.properties to add Timer to component palette.
Fine with me, especially since sampledir already is part of usersguide.
Thanks, Patrick...
... done.