[JBoss JIRA] Created: (TEIID-651) teiid-6.0.1-embedded-dist.zip: version of jar in run.bat/run.sh is out-of-sync
by Dave Malcolm (JIRA)
teiid-6.0.1-embedded-dist.zip: version of jar in run.bat/run.sh is out-of-sync
------------------------------------------------------------------------------
Key: TEIID-651
URL: https://jira.jboss.org/jira/browse/TEIID-651
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Affects Versions: 6.0.0
Environment: RHEL 5.3
java version "1.6.0_0"
IcedTea6 1.3.1 (6b12-Fedora-EPEL-5) Runtime Environment (build 1.6.0_0-b12)
OpenJDK Server VM (build 1.6.0_0-b12, mixed mode)
Reporter: Dave Malcolm
Assignee: Steven Hawkins
teiid-6.0.1-embedded-dist.zip (md5sum 8c8e8d6e3513ca88fbd302be9750943d)
contains this file:
- teiid-embedded-6.0.1/examples/portfolio/run.sh
Attempting to invoke run.sh leads to this error:
Exception in thread "main" java.lang.ClassNotFoundException: com.metamatrix.jdbc.EmbeddedDriver
Appears to be a version mismatch: run.sh contains this line:
TEIID_PATH=../../teiid-6.0.0-client.jar:../../deploy:../../lib/*:../../extensions/*
However, the zipfile contains the file ../../teiid-6.0.1-client.jar (note the difference in version; 6.0.0 vs 6.0.1).
I see a similar issue in the run.sh file (not tested though)
--
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
16 years, 6 months
[JBoss JIRA] Created: (TEIID-672) Replace homegrown Logging with Log4J
by Ramesh Reddy (JIRA)
Replace homegrown Logging with Log4J
------------------------------------
Key: TEIID-672
URL: https://jira.jboss.org/jira/browse/TEIID-672
Project: Teiid
Issue Type: Task
Components: Common
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
Teiid has Logging framework as well the implementation that supports the frame work, like Log Listeners, File appenders and Rolling File appenders, Platform loggers etc. Except for LogManager.java and its required constants, everything else can be replaced with Log4J implementation.
Designer seems to be only dependent upon the "Logger" interface, so that will be kept.
A "log4j.properties" configured for "embedded" and "server" runtimes to configure the logging destinations.
--
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
16 years, 8 months