>>> 3. Create an SPI in Pivot, to which one can plug in an underlying >>>implementation. You will need a bit of 'bridge code', which you stick >>>in SF. >> >> The skin essentially serves this purpose. If we have to, we can pretty >> easily remove it and source it elsewhere. > >You are not allowed to have; > >Pivot --> SFproj --> GPL/LGPL-proj > >where "-->" means dependsOn. But you ARE allowed to do so called >bridge implementations; > >Pivot <-- SFproj --> GPL/LGPL-proj > >Notice that the Pivot project is "free" from the viral effects, which >travels along the dependency graph. >For this to work, you typically create some form of SPI which will >take advantage of some type of plugin that is providing the >functionality you are looking for. From ASF legal perspective, it is >important that "Pivot" will work without using the 'plugin'.
This change has been submitted. The charting library has been decoupled from JFreeChart and now uses a provider approach to dynamically load chart skin implementations. The 1.1 distribution artifacts no longer contain any references to JFreeChart and do not require the presence of JFreeChart in order to build. A separate JAR file is now generated that contains the JFreeChart provider and is not included in the distribution. We will make it available to users in the Downloads section on Pivot's Google Code site.
