[
http://jira.codehaus.org/browse/MEVENIDE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110046 ]
Emilian Bold commented on MEVENIDE-563:
---------------------------------------
I'd like to add that using the palette with the JARs from the repository also doesn't work. I'm able to use the same custom Bean in a standard J2SE project, but with a maven project (which has all the dependencies), it doesn't work.
It might be that the Palette manager also looks at the "dependencies" of the parent project for the form file and sees if it can instantiate the bean. I assume the Maven project doesn't provide this.
For example, in a normal J2SE Project I need to add the "Library" (where the bean resides) as a dependency otherwise the form editor doesn't work.
Thus, while the Palette manager might be able to register javabeans using the repository JARs, it still won't be able to instantiate them if all those JARs don't show up as some dependency.
This is really annoying as I've learned to use the custombeans a lot and now I can't edit any form (I need to move the form to another temporary project in order to edit it).
AntArtifact.getArtifactLocations() might be what I need...
> Maven project doesn't work with Palette Manager
> -----------------------------------------------
>
> Key: MEVENIDE-563
> URL:
http://jira.codehaus.org/browse/MEVENIDE-563> Project: mevenide
> Issue Type: Bug
> Components: mevenide2-netbeans
> Affects Versions: NB_2.2
> Environment: Java 5, OSX, NetBeans 5.5.1, latest Mevenide from the update center
> Reporter: Emilian Bold
> Assignee: Milos Kleint
> Fix For: NB_FUTURE
>
>
> The NetBeans form editor allows users to register their own components.
> But Maven2 projects can't be used at all. Opening a JavaBean and selecting Tools->Add to Palette... gives an error that it can't be used.
> Normally the Palette Manager should be able to use either the classes from targer/ or the JARs from the local maven repo.
> From the little code I've read in the Palette Manager classes, it uses the project's classloader. Perhaps this is what's missing (or maybe it's more subtle than that...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email