[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:46:18 EDT 2011

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

Richard Kennard commented on SEAMFORGE-156:

Note an equally 'correct' thing to do (and much easier :) might be to just stay with metawidget-all, and wait for AS 7 to fix their bug. It is, after all, a serious bug that will need to be fixed for more than just Metawidget. I can't imagine AS 7 can go 'final' without fixing it.

The bug is related to JBoss classpath scanning not properly ignoring errors. JBoss AS 6 had a similar thing. There, you could configure which errors to ignore in scanning-deployers-jboss-beans.xml. I believe Jason Porter was filing a JIRA?

> 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