SVN access and issue tracking thanks to google code
Published by admin on Tuesday, February 16, 2010 - 05:45:57 - Filed under General, News
Hi all,
I’ve seen that the last post provoked some reactions, for which I thank you all.
I welcome Paul Bakker’s new “Product Manager” role in Servoy and wishes him the best for his difficult (yet essential) task. “working closely with the community”, this sounds good indeed!
I can assure everyone that I am totally willing to “work closely with Servoy”.
As another step again, I have started opening google-code projects for all my plugins and beans as a convenient way to access their sources using SVN (and submit patches, why not?), or even browse online (for the curious :), and for issue tracking/feature requests capabilities (you know you always want more ;-)
Right now you can find the sources of:
* the DnDFileBean http://code.google.c … -stuff-dndfile-bean/
* the keyListeners plugin http://code.google.c … keylisteners-plugin/
* the SVGBean http://code.google.c … ervoy-stuff-svgbean/
* the whois plugin http://code.google.c … -stuff-whois-plugin/
* the SliderBean http://code.google.c … -stuff-servoyslider/
* the DateChooserBean http://code.google.c … ff-datechooser-bean/
As for the busy plugin, it is already available:
http://code.google.c … /servoy-busy-plugin/ where Scott Butler opened it a while ago.
I have updated it this week-end to make it work with Servoy 5 and add a textColor property.
I’m using Mylyn in my Eclipe IDE and so automatically receive any bug report, feature requests, updates on issues right in my Task list, so you know that I will be notified quickly and that a task will be assigned to your issue.
I also tentatively opened a code project for the Browser Suite although I doubt that it will be enough, knowing that this stuff is composed of 4 inter-dependent projects:
- BrowserSuite (the main one, with the plugins and the beans)
- BuildAndDeploy (the installer project, package, sign the jars and build the installer)
- ServoyUtils (utility stuff detached from the suite, but used by plugins, beans and XULInstaller)
- XULInstaller (the XUL deployer project, used by the installer and by the smart client too)
All these projects use the build-in Eclipse ant tool for build, and some properties will need to be edited to match different configurations.
There are also a certain number of dependencies which I’m not sure if I can/will put into the SVN repository, although not doing so will complicate the settings (having to retrieve the correct build of SWT, DJNativeSwing and DJNativeSwing-SWT, XULRunner, JNA, IZpack, MozillaInterfaces and MozillaGlue, as well as the JavaScript Html editor - when so much depends on matching versions).
And you can also provide your own keystore and/or certificate to sign the whole thing.
Maven could be an answer to that, but I’m afraid I’m not Maven aware, although I can see its benefits, maybe I will need to dig into it.
If anyone has ideas on how to package all this efficiently for easy access without requiring 10 pages of doc on how to install, I welcome any suggestions!
