Hi, for example in Pivot all the drawing/graphics code uses AWT and Graphics2D features, available in Java 6 ... introducing a dependency on SWT (and a lot of "external" packages, not used by existing classes) to me seems wrong, at least in the core package.
Oh, Greg just answered like me :-) . So, what do you think on move all that code inside a (new) subproject inside the trunk (but I'd prefer to keep it in the Google Code site) ? In this way maybe we could leave the build as is, and these projects should only depend on existing jars (where possible, otherwise regenerate them). But a question: instead of fragmenting Pivot extensions in more sites, what do you think to refactor the existing pivot-jfree Or create a new (pivot-stuff, pivot-extensions, etc) ? And then move there the pivot-jfree and the other (pivot-eclipse, pivot-osgi, etc), as independent subprojects there ? And last, who better than our Pivot "President" to open and have the rights in that site (maximum respect :-) ) ? Comments ? Bye, Sandro
