[ https://issues.jboss.org/browse/JBIDE-10708?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10708: ------------------------------------- Forge should be able to augment any of the JBoss Central Maven-based archetypes: Java EE Web, Java EE, HTML5, RichFaces, SpringMVC and OpenShift. Mostly I would like entity generation but sometimes I also want scaffolding and JAX-RS endpoint generation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10710?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-10710: ------------------------------------- Beta5 is working. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10710?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-10710: -------------------------------------------- Hey Max, I'd rather just implement source scanning, the proper solution - imo. For now, if people really want to use Forge and Eclipse for something at the same time, they can just type "blah setup" which will add the blank activator that Forge expects. If that's a blocker, then we can talk about this, but if not, Forge needs to be locking down and stabilizing for Final release soon. I don't think this will make it for Final if we don't absolutely need it. I agree it needs to be solved, but more and more keeps getting added to Final and it's adding up :) We had originally said that we would only ensure apps-created with Forge deploy against AS7; now we're talking about making sure Forge works on every Archetype without any extra config, and I think this is a bit much creep for Final. However, if you have someone that has time to work on this for Final, I'll be glad to assist as much as possible! If we really want to hack it, we could add a facet override that allows manual installed/not installed settings for individual facets by name. E.g: `forge> project list-facets` ~Lincoln -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10710?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10710: ---------------------------------------- Summary: Forge not recognizing/enabling its features on "plain" projects/archetype (was: ***ERROR*** [entity] Plugin is not usable in current scope or project.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10710?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10710: ---------------------------------------- Component/s: forge -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira