Introduction
In this page, it aims to provide more design issues for astyle eclipse plugin
Development
Code
format engine comes from astyle, the lastest version is 1.19,
but the used in astyleclipse now is 1.14.
The Mud 1.1.0 release plan to port 1.19 to java, since there is no request, it is paused.
The plugin part comes from CDT indent plugin, which looks great for a base
Eclipse-LazyStart=true is used in eclipse 3.2, while Eclipse-AutoStart is used in eclipse 3.1, which is deprecated in eclipse 3.2, so I keep two release
Preference page, preview use SourceView now, i don't know how to use CDT SourceView for preview (need syntax highlight)
It will be good to use profile and more checkbox to control the format options like java format, it needs more competence on jface, probably could wait for JFACE/JDT provides more API
Version control
Since subversion is the replacement of cvs, and it is supported in sf.net . it is selected. Subversive plugin is used to access it, there is another subversion plugin subclipse, but it seems subversive is more productive
Probably could use fisheye for web access subversion
Quality control
cenqua provides clover plugin, which is a powerful Java code coverage analysis tool for free.
Update site
Most of things can be done in eclipse, it also suggest to update the update-site.zip for other integrators
- create feature project to contain the plugin, fill needed license/copyright issues
- create update project to contain the feature, after build all
- use WinSCP to upload all the contents into sourceforge.net
Process
Reference
- Preference field ediotors : http://www.eclipse.org/articles/Article-Field-Editors/field_editors.html
- Version number : http://www.eclipse.org/equinox/documents/plugin-versioning.html
- How To Keep Up To Date http://www.eclipse.org/articles/Article-Update/keeping-up-to-date.html
- Plugging into SourceForge.net http://www.eclipse.org/articles/Article-Plugging-into-SourceForge/sourceforge.html