[forge-issues] [JBoss JIRA] (FORGE-348) Update MetaWidget dependencies to not bring in metawidget-all

[M Chisty (Commented) (JIRA)]

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

M Chisty commented on FORGE-348:
--------------------------------

Using forge, it is expected that using Metawidget should be an option, not a mandatory feature. 

However this was found that when we use Forge to create a SEAM3 project from scratch, we must use metawidget. We have to understand the fact that Metawidget just creates some auto-generated xhtml codes from POJOs (good for simple CRUD based apps). But real life project is much more complicated. It is not always the direct table -> POJO - > xhtml mapping. 

What if we don't need metawidget at all, but we still want to use Forge to build up SEAM3 project using Richfcaes, JB7 etc... Do we have the option? Do we always need to use metawidget and then remove the config files (metawidget releted) manually to make our project metawidget free? 
                
> Update MetaWidget dependencies to not bring in metawidget-all
> -------------------------------------------------------------
>
>                 Key: FORGE-348
>                 URL: https://issues.jboss.org/browse/FORGE-348
>             Project: Forge
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>            Assignee: Lincoln Baxter III
>             Fix For: 1.0.0.Alpha4
>
>
> We don't need MetaWidget-all, which will also bring in Spring core classes (breaking in AS7 deployments).

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