The main sources are packed with the wingS distribution. We believe that for optimal development efficiency you should always have the sources of the underlying frameworks at hand, just in case some things need deeper clarification.

Source Repository

But if you want to be in touch with the latest developments you can always check out the current CVS version via Subversion. The SVN root is

For SVN command line based checkout try:

Refer to Join for informations how to join and commit into the wingS SVN repository.



wingS requires the following software to run properly:

  • Java 1.5 or later
  • Apache Tomcat 5.0 or later
  • Ant 1.6 or later; make sure it is included in the PATH environment variable


Building wingS

In order to build wingS, try the following steps:

  • checkout wings2 from SVN (use trunk) or download and unzip a wingS release
  • copy the wings2/etc/ to etc/
  • set the path to tomcat in the file to your tomcat home directory
  • Now build wingS and the wingset demo by executing the following commands


cd wings2
cd demo/wingset
ant deploy


wingX is a set of enhanced wingS components working on top of wingS. Its intention is to keep the core wingS framework clean and small and close to Swing. wingX should be a repository for more web-centric and/or wingS proprietary components like i.e. a filterable and sortable table, a calendar component, etc. wingX especially addresses you: wingX is liberally open to contributions.

Building wingX

In order to build the wingX components and include them in the wingSet demo, try the following steps. This assumes that you have already set up wingS as explained above.

  • checkout wingx2 into the same top level directory as wings2 (use trunk)
  • copy the wingx2/etc/ to etc/
  • set the path to tomcat in the file to your tomcat home directory
  • Now execute the following commands
cd wingx2
cd demo/wingxet
ant deploy
  • Start the tomcat server and it should run fine.