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.
[ BUILD # : Beta1 ] [ JDK VERSION : J2SE 1.5.0 ] When selecting a bean to add to the palette from either the "projects" window or "file window," and I either select via context menu or from teh menu bar "Add to Palette..." The component is not added to the palette. I do get the popup asking me which category to add it to, but it is never added. No stack traces are reported to the messages log either. I am using the freeform project type, with the appropriate result jars and paths setup in output dir.
I am sorry, I am not able to reproduce this issue. Could you, please, provide more details about configuration of your project. Does it happen only with one project/only with freeform projects? It would be great if you can provide steps describing how to set up such a problematic project. Thank you in advance.
Created attachment 17090 [details] Test Case, full project zip
Added a test case on 4.0beta1 JDK1.5.0 beta 3 (build 58) Windows 2000. In projects or files, on either the java class or the .class file, it's not added. If I use palette manager and add jar I can add the bean.
Thank you for the test case. Now I was able to reproduce the problem. When we try to install the bean we attempt to find the jar the bean comes from. Unfortunately the call AntArtifactQuery.findArtifactsByType(project, "jar") on the freeform project doesn't return anything because it doesn't have AntArtifactProvider. Reassigning to ant module for evaluation. Is this as designed? If so, how should we find the right jar?
But propaly isn't a P2. David please decide.
Jesse knows more about why freeform does not have AntArtifact and whether it should or not. I guess that if output jar is specified that we should provide it.
There is no AntArtifactQueryImplementation in freeform projects for 4.0. You can use the Palette Manager. Anyway using AAQ for such a purpose is wrong. A future release will probably have a BinaryForSourceQuery in which case you can use that. The form module needs to handle this case properly: issue #47947.
Actually meant this to be open for 4.1.
Hold on; <export> element already allowed in freeform project.xml, just not yet interpreted. May be able to do this for 4.0 after all. (No GUI configuration for it, however; you would need to set it up manually in 4.0.)
There is an "output" node in the properties sheet, that palces the jars in /project/configuration/java-data/compilation-unit/built-to. I honestly would expect that those values are what are exprted, so wouldn't the GUI just be the same as that page? Couldn't the customize just add those entries in addition to it's compilation-unit entries?
*** Issue 48126 has been marked as a duplicate of this issue. ***
Perhaps. The <export> element includes more information than the current GUI asks for so it would not be able to set things up as precisely as you could by editing project.xml. It may be possible to make guesses that work out most of the time.
*** Issue 49012 has been marked as a duplicate of this issue. ***
Have patch which makes it work if you configure the <export> element(s) in project.xml. Tools -> Add to Palette works (AFAICT), and you can add the freeform project as a dependency of a j2seproject (code completion, building, and rebuilding all work).
See issue #49221 for GUI updating of <export>.
added * Up-To-Date 1.1 ant/freeform/src/org/netbeans/modules/ant/freeform/ArtifactProvider.java committed * Up-To-Date 1.28 ant/freeform/src/org/netbeans/modules/ant/freeform/FreeformProject.java committed * Up-To-Date 1.11 ant/freeform/src/org/netbeans/modules/ant/freeform/resources/freeform-project-general.xsd added * Up-To-Date 1.1 ant/freeform/test/unit/src/org/netbeans/modules/ant/freeform/ArtifactProviderTest.java committed * Up-To-Date 1.2 www/www/ns/freeform-project/1.xsd
*** Issue 49389 has been marked as a duplicate of this issue. ***
Works in dev build 2004091800