David,
I remember that
IBM has a request to support the start tracing to pass Rational Compatible Test
or something. It means each plug-in should read the .option from the plug-in
home and print out the logging information to the console. We implement this
feature in the Activator of the plugin.
So I think you
should not remove the ChartEngineActivator
from the chart engine, remove it from the chartapi.jar is enough.
From:
birt-dev-bounces@xxxxxxxxxxx [mailto:birt-dev-bounces@xxxxxxxxxxx] On Behalf Of David Michonneau
Sent: Friday, April 28, 2006 5:37
AM
To: For developers on the BIRT
project
Subject: [birt-dev] Checkin: BIRT
Chart - Removed org.eclipse.core.runtimedependency from chart engine code
-
Summary:
Removed org.eclipse.core.runtime dependency from chart engine code
- Bugzilla Bug (s)
Resolved:
None
- Description:
Removed ChartEngine activator class to
remove direct eclipse.core.runtime dependency. The Chart Engine plugin now has
no direct dependency on eclipse.core.runtime (there is still an indirect one
through birt.core though). That will avoid OSGi exceptions in configurations
where the eclipse.core.runtime plugin is not available on OSGi client side
(those exceptions do not prevent OSGi to load chart extensions, but are just
unnecessary)
- Tests Description : Unit tests. UI Tests
- Files Edited:
"/org.eclipse.birt.chart.engine/META-INF/MANIFEST.MF"
-
Files Added:
-
Files Removed:
"/org.eclipse.birt.chart.engine/src/org/eclipse/birt/chart/plugin/ChartEngineActivator.java"
-
Notes to I18N Team:
-
Notes to Build Team:
- Notes to Developers:
- Notes to QA:
- Notes to
Documentation: