JCL Download

From Project JEDI Wiki
Jump to navigationJump to search

You can download the Jedi Code Library directly from SourceForge.net. We offer a complete source pack, preview (a. k. a. development) versions, access to our version control system and additional documents & tools.

Official stable releases at Sourceforge

You can download official stable files from the JEDI Code Library at Sourceforge.net

Source code archives

The JCL is split into several archives, you may download one of the source code archive:

To install the JCL, extract the archive and execute "install.bat" (Windows).

DLL archive

If you plan to use the 7z wrapper or the zlib, bzip2 or pcre DLL, you may download:

  • jcl-2.4.1.4571-dll.zip all the DLL dependencies. These DLL are intended to be placed in your application directory.

Help archives

You may download one of the help archive:

To install the JCL help into the IDE help (htmlhelp2 or winhelp only), extract the archive into your JCL directory and run the installer again, check the help nodes and reinstall the JCL.

Unstable JCL tarballs

Source daily zips and help weekly zips can be downloaded at http://sf.jcl.delphi-jedi.org/daily. These files are generated at about 07:30AM UTC (GMT) from our version control system. These files can be extracted using the free sevenzip tool.

Source daily zips

To install a JCL daily zip, uninstall any previous version of the JCL, download and install one of the following files, then run "install.bat".

http://sf.jcl.delphi-jedi.org/daily/index.php?xml=yes
http://sf.jcl.delphi-jedi.org/daily/

Your web browser does not support cross-domain AJAX, see the file list at http://sf.jcl.delphi-jedi.org/daily/

name (size, automatically generated on date)

Help weekly zips

To install one the help weekly zips (htmlhelp2 and winhelp only), extract the help archive first into your JCL directory, then run "install.bat", select the help nodes and reinstall the JCL.

http://sf.jcl.delphi-jedi.org/daily/index.php?xml=yes
http://sf.jcl.delphi-jedi.org/daily/

Your web browser does not support cross-domain AJAX, see the file list at http://sf.jcl.delphi-jedi.org/daily/

name (size, automatically generated on date)

Direct access to our version control system

The JEDI Code Library Team uses GIT for Version Control. To always have access to the most recent changes in the JCL, you should install a GIT client (we recommend TortoiseGIT). GitHub provides a transparent read-only SVN mirror that users may use for external linking from their SVN repositories.

Stable versions (tags)

The latest stable of the JCL is located at JCL-Latest tag https://github.com/project-jedi/jcl/tree/JCL-Latest. GIT users need to fork the complete repository at https://github.com/project-jedi/jcl.git and switch to this tag. SVN users can directly checkout this tag at https://github.com/project-jedi/jcl/tags/JCL-Latest.

All the past and present stable versions of the JCL can be accessed using one the tags listed in https://github.com/project-jedi/jcl/releases. GIT users need to fork the complete repository at https://github.com/project-jedi/jcl.git and switch to the desired tag. SVN users can directly select and checkout the desired tag at https://github.com/project-jedi/jcl/tags/.

Unstable main version (trunk)

You can download the GIT repository files to your computer by forking the repository at https://github.com/project-jedi/jcl.git. A transparent read-only SVN mirror is available at https://github.com/project-jedi/jcl/trunk.

With the GIT or SVN client, you can update your local repository at any time.

Other development tests (branches)

For testing changes that may break the backward compatibility of the JCL, JCL developers commit their changes to dedicated branches. Their list is located at https://github.com/project-jedi/jcl/branches.

Web access

You can also access the GIT repository via the web using GitHub interface.

Changes notifications

If you want to be informed when changes are made in the JCL source code. You may subscribe to the JCL mailing lists where messages are automatically sent each time files are modified in the JCL subversion repository:

  • The mailing list jcl-checkins broadcasts the changes without many details (short emails);
  • The mailing list jcl-checkins-diff brocasts the changes with details included (big emails).