[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-156) Update MetaWidget dependencies to not bring in metawidget-all

Richard Kennard (JIRA) jira-events at lists.jboss.org
Mon May 2 19:29:18 EDT 2011


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

Richard Kennard commented on SEAMFORGE-156:
-------------------------------------------

Note the 'correct' thing to do in this case is for Seam Forge to edit the POM to bring in metawidget-faces.

But then you will need Seam Forge to *further* edit the POM to bring in metawidget-richfaces (if they opt for RichFaces), metawidget-jpa (if they opt for JPA) etc etc. Some of these dependencies supersede each other (ie. you don't need to specify metawidget-faces if you already specify metawidget-richfaces) but it's no big deal if you bring in them both.

> Update MetaWidget dependencies to not bring in metawidget-all
> -------------------------------------------------------------
>
>                 Key: SEAMFORGE-156
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-156
>             Project: Seam 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the forge-dev mailing list