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

[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Richard Kennard edited comment on SEAMFORGE-156 at 5/2/11 7:45 PM: ------------------------------------------------------------------- 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 missing classes. 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? was (Author: kennardconsulting): 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? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira