[
http://jira.codehaus.org/browse/MEVENIDE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milos Kleint updated MEVENIDE-563:
----------------------------------
Fix Version/s: NB_FUTURE
the problem is the action requires the project to implement AntArtifact interface which the Maven support cannot provide.
I've filed as
http://www.netbeans.org/issues/show_bug.cgi?id=118694 in netbeans issuezilla. Nothing can be done on mevenide side. A possible workaround is to add the beans to palette directly from the repository jar.
> 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
