[ https://jira.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen updated JBIDE-6608: --------------------------------------- Assignee: Brian Fitzpatrick (was: Kris Verlaenen) Fix Version/s: 3.2.0.M2 Not sure if we can do this for M2, but we could at least start getting Drools natures/ui to behave "nicely". i.e.first step would to Move enablement of Drools into the Configure menu (requires Eclipse 3.5+) second step is to introduce a Drool facet to make it possible to enable on WTP projects. That facet would simply add/remove the appropriate nature in the first "edition". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBIDE-6608: ------------------------------------------ The Configure menu move is easy... I agree that moving the Convert to Drools Project menu under Config makes sense. An example of how to do that is in the Struts UI plug-in xml... <extension point="org.eclipse.ui.popupMenus"> <objectContribution ... <action class="org.jboss.tools.struts.ui.internal.action.AddStrutsNatureActionDelegate" enablesFor="1" icon="$nl$/images/xstudio/actions/add_struts_nature.gif" id="org.jboss.tools.struts.ui.action.AddStrutsNatureActionDelegate" label="%popupMenus.action.addStrutsNature" menubarPath="org.eclipse.ui.projectConfigure/additions"> </action> </objectContribution> ... </extension> But I have to wonder about removing the Drools nature... Looking at the Config menu there doesn't seem to be a way to remove other project natures or facets directly there - you're adding functionality or configuring a project to work for a particular technology, but not really removing anything. You can however, as Max mentioned, remove a facet after it's been configured. Kris, do you want to look into defining a Drools facet that would be configured instead of the project nature? It would by default then have a way to (in the project properties) remove the facet if they wanted to "un"-configure it. Perhaps we spin that off into a separate JIRA and for now just move the Convert to Drools Project under the Config menu ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBIDE-6608: ------------------------------------------ Thanks Kris. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin.s... ] Kris Verlaenen commented on JBIDE-6608: --------------------------------------- Added temporary solution by moving the Convert action to the configure sub-menu. Changed fix version to LATER until we figure out how to solve this better. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin... ] Max Andersen commented on JBIDE-6608: ------------------------------------- Iain, I agree it should be possible to remove but for now it's not an option. Patches welcome. As a workaround simply open .project and remove the drools nature and builders and it should be gone. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin... ] Iain Shepherd edited comment on JBIDE-6608 at 1/4/11 8:53 AM: -------------------------------------------------------------- Thanks for your reply Max. Yes, that was my first thought; I reverted changes to .project and .classpath, this caused a 'Could not find default Drools runtime' error. I tried several times closing/reopening the project, cleaning it, restarting Eclipse, etc. but the error persisted. I could only assume there is some change in the workspace metadata dir that I needed to revert too, but I didn't have time to track it down, and deleting/reimporting the project fixed the problem. (As per the thread linked above) (Edit to add) now find that I've lost all my breakpoints, due to the delete/reimport requirement was (Author: ishepherdms): Thanks for your reply Max. Yes, that was my first thought; I reverted changes to .project and .classpath, this caused a 'Could not find default Drools runtime' error. I tried several times closing/reopening the project, cleaning it, restarting Eclipse, etc. but the error persisted. I could only assume there is some change in the workspace metadata dir that I needed to revert too, but I didn't have time to track it down, and deleting/reimporting the project fixed the problem. (As per the thread linked above) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin... ] Libor Zoubek updated JBIDE-6608: -------------------------------- Fix Version/s: (was: 3.2.x) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira