From: Chris G. <ch...@go...> - 2003-04-14 13:27:11
|
> I think the svgtest branch basically works, though we need more SVG > images. (I'll try to make some tonight.) Unfortunately, because it's > a CVS branch, probably only 2 or 3 people have tried it, not a great > test sample. We need to get it merged into the trunk, then get a > SVG-enabled release out, before we're likely to get much wider testing. > > Do you want me to merge the branch ? It will requires Batik to > compile, so we need to warn CVS users... Is that really necessary? Can't the batik libraries be simply included in the project in the same way that sax libraries were for the java-1.3 version? Or is it possible to manage a subproject within sourceforge? In this case you would only need the appropriate "release" of the SVG code when compiling the rest of the colossus code. Then only the developers working on the SVG code would need to have the batik tools installed. I am concerned about adding a requirement to the build process to support a feature that is optional in the end product. |