[
https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin....
]
Lincoln Baxter III commented on FORGE-604:
------------------------------------------
Hey Chris!
Thanks so much for reporting. Do you think you might be able to add a brief description of
what Forge does incorrectly when operating on an EAR? Also perhaps attach a sample project
that we can reproduce the functionality with?
I know this is asking a lot, but it would really help us get things working!
Thanks,
Lincoln
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: Future
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira