Menu

Tree [r174] /
 History

HTTPS access


File Date Author Commit
 soap-dust 2012-10-05 pascal [r174] minor
 www 2012-02-14 pascal [r171] ADD how to encapsulate input output stream
 README 2011-03-18 pascal [r90] ADD script to deploy soap-dust web site
 TODO 2012-10-05 pascal [r174] minor
 update-soap-dust.sf.net 2011-03-18 pascal [r90] ADD script to deploy soap-dust web site

Read Me

/trunk /tags /branches svn convention is not used in this project.
This is the convention we use in soap-dust :

1) web site
-----------

/www/htdocs contains the source of the web site. Javaodc is generated in this directory.

To update the web site:
* first ensure that all your modifications are committed in www directory
* then run update-soap-dust.sf.net

2) source code
--------------

The source code of a module is stored in:

/<module>/<major.minor version>/

So for instance if you want to work on version 0.0 of soap-dust, you will have to check out:

/soap-dust/0.0/

If you need to release a new version 0.0 of soap-dust, you just have to:
 1) go into /soap-dust/0.0/
 2) check in svn all your local modifications
 3) run ant release

That's it ! The new jar file is available in your target subdirectory and all information
that may be needed to find the originating sources is available in the jar file name.

If you want to check source code of the jar file soap-dust-0.0.45.jar, you will find everything
you need here :

 $> svn co https://soap-dust.svn.sourceforge.net/svnroot/soap-dust/soap-dust/0.0@45 soap-dust-0.0.45

Have Fun!
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.