[
https://issues.jboss.org/browse/SEAMFORGE-362?page=com.atlassian.jira.plu...
]
Lincoln Baxter III commented on SEAMFORGE-362:
----------------------------------------------
However, for most plugins, you shouldn't need to restart in order to gain access
(it's just that the HTools plugin does not work at all right now.) Again, sorry,
working on it.
Installing plugin hibernate-tools cause log4j failure due to class
loader conflict
----------------------------------------------------------------------------------
Key: SEAMFORGE-362
URL:
https://issues.jboss.org/browse/SEAMFORGE-362
Project: Forge
Issue Type: Bug
Components: Blessed Plugins
Affects Versions: 1.0.0.Beta3
Environment: Mac OSX 10.7.2, JDK 1.6.0_26 64bit
Reporter: Steve Tarver
Priority: Minor
Labels: hibernate-tools, log4j
On a fresh forge install, installed hibernate-tools plugin. Stopped forge. Started forge
and saw
[starver@makara isd-pkgferry 16:14:16]$ forge
log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable
to a "org.apache.log4j.spi.Configurator" variable.
log4j:ERROR The class "org.apache.log4j.spi.Configurator" was loaded by
log4j:ERROR [ModuleClassLoader for Module "org.jboss.forge:main" from local
module loader @320cf66b (roots:
/Users/starver/dev/forge-1.0.0.Beta3/modules,/Users/starver/.forge/plugins)] whereas
object of type
log4j:ERROR "org.apache.log4j.xml.DOMConfigurator" was loaded by
[ModuleClassLoader for Module
"org.jboss.hibernate.forge.hibernate-tools-plugin.dependencies:1.0.0-SNAPSHOT-cd6ef896-c37d-40a3-926f-b1d164a0a129"
from local module loader @320cf66b (roots:
/Users/starver/dev/forge-1.0.0.Beta3/modules,/Users/starver/.forge/plugins)].
log4j:ERROR Could not instantiate configurator [org.apache.log4j.xml.DOMConfigurator].
log4j:WARN No appenders could be found for logger (org.jboss.weld.Version).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira