[forge-issues] [JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

[Christopher Volk (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745520#comment-12745520 ] 

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
>From root project level:*
- 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.
                
> Add support for Java EE 6 Full Profile
> --------------------------------------
>
>                 Key: FORGE-604
>                 URL: https://issues.jboss.org/browse/FORGE-604
>             Project: Forge
>          Issue Type: Task
>          Components: Java EE APIs
>    Affects Versions: 1.0.5.Final
>         Environment: All
>            Reporter: Christopher Volk
>             Fix For: 1.2.0.Final
>
>
> Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging.
> The EAR packaging should be fairly "easy" to implement.  The maven side of multi-module should be similarly "easy".  CLI multi-module support is something I would expect to take up most of this effort.
> I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile.  I know that almost all the apps I work on professionally require Full Profile.  
> This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-)

--
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