[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ] Christopher Volk commented on FORGE-604: ---------------------------------------- Additional info based on running *Forge 1.1.3.Final* against a new multi-module maven project created in Idea (using JBoss BOMs), and ear packaging. Things are looking much better based on all the following, very-positive info. Can start forge in either root or module dir and it sees it as a project - Can build at base project level and sub module level - Can add a repo - Can add a dependency - Can add a managed dependency *Dependencies and plugins:* In module dir: $ cd myapp-web - "project add-dependency" will successfully find managed dependencies in parent pom and ask if we want to use it (sweet!) - listing facets is properly module aware - "primefaces setup" works if you cd into web module, complains about war vs pom types if run from root proj dir (not bad) - "persistence setup" works if cd'd into ejb module *Main thoughts:* We'd probably need something like: - EAR module support for things like new-project and --type - Add multi-module maven support with appropriate sub module setups/poms - EAR packaging support - Make "CLI scoping" more module aware - Should better handle (prevent? auto-cd?) running module-specific (e.g. JSF) plugins/commands at parent pom level I hope this helps a bit. I'll try to attach a project to play with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira