[jboss-jira] [JBoss JIRA] (WFLY-2926) Missing dependency to com.google.guava in jberet
James Perkins (JIRA)
issues at jboss.org
Thu Feb 13 17:55:29 EST 2014
[ https://issues.jboss.org/browse/WFLY-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Perkins updated WFLY-2926:
--------------------------------
Workaround Description:
Add the {{com.google.guava}} to the {{module.xml}} for the JBeret module.
Path to file
{code}
$JBOSS_HOME/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
{code}
XML with the added module
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="org.jberet.jberet-core">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="jberet-core-1.0.0.Final.jar"/>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javaee.api"/>
<module name="javax.transaction.api"/>
<module name="org.jboss.jts"/>
<module name="org.jboss.marshalling"/>
<module name="org.jboss.logging"/>
<module name="com.h2database.h2" optional="true"/>
<module name="com.google.guava"/>
</dependencies>
</module>
{code}
Workaround: Workaround Exists
> Missing dependency to com.google.guava in jberet
> ------------------------------------------------
>
> Key: WFLY-2926
> URL: https://issues.jboss.org/browse/WFLY-2926
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Batch
> Affects Versions: 8.0.0.Final
> Environment: Oracle JDK7u51
> OS X 10.9.1
> Reporter: Kyle Shanahan
> Assignee: James Perkins
> Priority: Minor
> Fix For: 8.0.1.Final
>
>
> jberet uses guava but the module.xml does not declare a dependency on it. it makes occur unexpected exception java.lang.NoClassDefFoundError: com/google/common/base/Throwables
> I reported about it in a website http://www.nailedtothex.org/articles/jbatch/wildfly8finalguava/
> (it wrote in Japanese, but stacktraces are may be useful)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list