[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3303) Unable to deploy war in JBoss AS due to jgroups dependency

Pete Muir (JIRA) jira-events at lists.jboss.org
Sun Aug 24 06:59:38 EDT 2008

    [ https://jira.jboss.org/jira/browse/JBSEAM-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12426332#action_12426332 ] 

Pete Muir commented on JBSEAM-3303:

Ok, I fixed this in trunk.

I'm not sure whether the snapshots builds are running as we in a code freeze in prep for release.

Best bet is to grab trunk and build yourself. You'll need to then point at org.jboss.seam:jboss-seam:2.1.0.BETA1 in maven.

> Unable to deploy war in JBoss AS due to jgroups dependency
> ----------------------------------------------------------
>                 Key: JBSEAM-3303
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3303
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.1.0.A1
>            Reporter: Michael Neale
>            Priority: Blocker
>             Fix For: 2.1.0.BETA1
> We are using maven snapshots, since thursday (ish) have seen this when deploying a war: 
> ]20:13:35,132 INFO  [STDOUT] ERROR 24-08 20:13:35,126 (DependencyManager.java:checkClassDependencies:151)         Error while checking dependencies for component class org.jboss.seam.cache.JbossCacheProvider
> java.lang.NoClassDefFoundError: org/jgroups/MembershipListener
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:675)
>         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>         at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>         at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> (Shane B knows about this).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list