Cricket And The Ant Mac OS

THE AND AND THE CRICKET watch and subscribe our channel EVOKE KIDS ZONE. Browse other questions tagged ant mac-os-x or ask your own question. The Overflow Blog Mint: A new language designed for building single page applications.

Build And Deploy With Ant On Mac OS X

Build multi-platform Java distributables and deploy them to a server with Apache Ant on Mac OS X

While Java is a useful language to write cross-platform code, you would be better off providing customized executables and distribution packages, to avoid unnecessarily limiting your user group to experienced computer users, who know how to install a Java Runtime and the like. Also consider, that some people may even not have the right to install something. The intention here is, of course, to deliver distributables, that can be used by literally anyone. But, while you want to reach as many customers as possible, you also have to keep the number of different distributions as small as possible in the same time, dependent on the amount of resources you can investigate in creating, maintaining and testing your product.

One of my current projects also supports users with any kind of experience in computer usage. As it is a single-person and non-commercial project, I have to keep the costs low overall. In order to still reach the mentioned goals, I needed to set up a few constraints:

The executable program should:

-) be delivered as a single-file standalone executable (that means without dependencies on other programs or libraries that might not be installed on target systems),
-) allow users to recognize it as a 'platform-native program',
-) start by double clicking,
-) not need to be installed (copying it somewhere should be sufficient) and
-) be executable without any administrative permissions.

Naturally, this translates into different solutions for the platforms, that I have chosen to support:

WINDOWS solutions:
1) Providing an EXE file, that contains all needed bits (including its own JRE). Because of the file size being quite big, and because of the requirement to be install-free, I decided to go for a self extracting executable (using the 7z format because of its good compression rate), satisfying all initial constraints from above and running on all Windows versions from Windows 2000 to Windows 7.
2) Because of the big difference in file size and because the Java Runtime is already installed on many computers, I am also providing a lightweight EXE file that is dependent on an installed JRE, but would pop up an error message containing a download link, if the required Java Runtime is missing. Also supports all Windows versions from Windows 2000 to Windows 7.

MAC OS X solution:
3) First, delivering a native application bundle is recommended for OS X. Then my choice to develop code based on Java version 6 automatically limits the target operating system versions to the 64-bit versions of Mac OS X Leopard (the 10.5 range) and all versions of Mac OS X Snow Leopard (the 10.6 range). Mainfighter mac os. Aside from the limit, this approach has the advantage, that the supported range of target systems all have the Java 6 Runtime preinstalled and in case of troubles it is easy to update these Java installations via the 'System Preferences > Updates' utility. This solution also satisfies all recommendations for executables from above.

'LINUX' solution:
4) Being the least important 'platform', I accepted some trade-offs, to make my life easier. At the other side, I suggest that there is a good chance anyway, that Linux users would manage to install Java, if needed. Also, many user-friendly Linux distributions like Ubuntu allow starting up JAR applications by double-clicking. So I am delivering a standard JAR application, that relies on an installed Java Runtime and that may not appear to be 'platform-native', but satisfies all other constraints. Moreover, this solution should run on any operating system with an installed JRE.

Distribution wise, I decided to use ZIP archives, to package the application together with important documents like installation notices, the license and a manual. It surely would be even simpler for the end-users, if I would let people download the executable file only, instead of a ZIP archive that must be expanded first. But then I would need to introduce a kind of installation routine, so that at least the license notice pops up. As I absolutely want to avoid any installation routines and nagging users anyhow, providing the ZIP archive with the license in the top hierarchy, so that users must notice the presence of the license, is my preferred way to go. Providing single-file executables, I also don't have to worry about users moving files around after expanding the archive.
Only for Mac OS X I am using the recommended Apples Disk Image format. Read the Mac OS X Human Interface Guidelines and also the Java Development Guide for Mac OS X for more information about developing and distributing Java applications on and/or for Mac OS X.

After setting the requirements, my next goal was to fully automate the build and deploy process on a Mac OS X machine, or at least as much as possible. To be honest, I am amazed by the result as it does more than I expected that would be possible. Just one small issue remained, that I could not automate on the Mac: Editing the Version Info of an SFX file to update the version numbers. There are plenty of resource hacking command line tools for Windows, but I did not find a single application for Mac OS X, that would work with Ant. All command line programs, I found for unix-like systems, use their own GUI and thus do not allow automation.

However, the resulting build file nicely satisfies my needs. Ire and ike mac os. Here is an overview about what it does:

1 ) Clean all files that were generated in previous build processes.
2 ) Rebuild the project entirely, that is:
2.1 ) Compile the Java sources.
2.2 ) Assemble additional required resources.
2.3 ) Generate Javadocs.
3 ) Save a project backup.
4 ) Produce the following distributables:
4.1 ) An executable JAR distro. I am offering it as the 'Linux version', as it should run on all operating systems with an installed JRE. This task only requires a standard Java Archive Tool jar, that comes with any JDK. The application is then delivered within a ZIP file, together with all the docs that might be useful for the end-user (installing instructions, license and manual).
4.2 ) A Mac OS X application bundle distro. The application bundle features a custom icon and a custom Info.plist (containing app name, short info, version info, copyright, bundle identifier,…), and the app is shipped together with the user docs in a nice laid out Apple Disk Image file (DMG file), having predefined Finder View Options – including a custom Finder window background – and a link to the Applications folder for easy installation. Requires JarBundler to generate the app bundle, hdiutil (using the preinstalled version on OS X 10.6.7) to create and deal with DMG Volumes and SetFile (part of the Apple Developer Tools, so most likely installed, if you develop software) to enable a custom folder icon for the mounted DMG volume.
4.3 ) A Windows native executable distro, that is dependent on an installed JRE. The EXE is wrapped by Launch4J, which also allows to customize the Version Info and the icon of the resulting EXE file. The executable is then also distributed inside a ZIP file, containing the same user docs as the other distros, but formatted using Windows standard line break characters (CR+LF instead of LF).
4.4 ) A standalone Windows native executable distro, that does not need to be installed and is completely independent from any existing (Java) installations, so that the user does not need to have administration permissions to run the application. I am using the SFX approach here, that I already discussed in another blog article. Requires p7zip, a SFX launcher module (e.g. from Oleg Scherbakov) and an app.tag file (also covered by my blog article mentioned above). The build procedure is quite simple, you only have to zip the JAR Java application and a complete Java Runtime to a 7z archive and then concatenate it with the SFX module and the app.tag file. The created EXE file is again distributed via ZIP archive, containing the required specific user docs. Note, that the docs of course differ from the other Windows user docs, because there are no Java dependencies and you have to incorporate the Java license and its requirements.
4.5 ) A source files distro. I am simply distributing the current project backup ZIP file.
5 ) Copy all distributables to a local backup.
6 ) Deploy all distributables to a remote server via FTP over explicit TLS/SSL (also known as FTP-SSL or FTPES) using curl, which comes preinstalled with OS X.

And these are the required steps that still need to be done manually to prepare for the Ant build process:

Cricket And The Ant Mac Os Pro

-) Make sure, that the version number and the publishing date properties in the build.xml show the correct numbers.
-) Fire up your (virtual) Windows machine and update the Version Info of the SFX launcher module (e.g. 7zSD.sfx from Oleg Scherbakov), which is needed for the standalone self extracting Windows executable. Don't forget to copy the updated module to the project folder afterwards.

After that, you can already run the Ant script, which is simply done by:

1) Open a terminal window
2) Change the directory to the project directory (build.xml should be located here).
3) Type 'ant all' and press the enter button… Attack of the killer dandelions mac os.

Depending on your script, the last step could take a while. My computer needs about 15 minutes to accomplish all tasks, but this is mainly caused by the ftp transfer tasks, because my homepage server is rather slow at reading data from ftp connections.

The build file is laid out to be portable, so if you are on Snow Leopard, you only need to download and install the necessary programs and libraries (those can be obtained for free and information regarding the installation can be found in the build file comments) and set the project property definitions in the upper part of the build file according to your project. The project property definitions are quite extensive to provide high portability, so it may take a while to get used to the structure of these definitions at the other hand.

The documenting comments in the build file should provide enough information and all the links to get you started, at least if you work on a Mac. On Windows i bet you will have a hard time creating a satisfying Mac OS X application bundle. That was also a good reason to accomplish the whole process on a Mac… only leaving the resource hacking problem. But the whole build process including the deployment is really easy-going now. Apart from this nice feature, the build process now is also a lot more reliable compared to manually putting the distros together and uploading them to the required destinations.

If you have problems understanding the build file, consider downloading the source files of my project YouTube Comments And Nicks Collector (at least the current version 1.0.1.16 was actually deployed with the example an build script from above) to figure out, how this all works.

Cricket Captain 2016 is the third version of the cricket team management game. It's time for cricket fans around the world to put their tactical expertise to the test in the most in-depth cricket management game ever made. Developed in association with Chris Rogers, captain of Somerset, Cricket Captain 2016 has more playable teams, new South African and New Zealand leagues, and more great features than ever before.

Cricket And The Ant Mac Os Download

Cricket Captain has been hailed as the best cricket management simulation and Cricket Captain 2016 takes the game to the next level with day/night matches, an updated interface, improved match engine and all the attention to detail that you expect from the series.

Features

• 79 playable domestic teams: across 5 domestic leagues, including 12 new teams in the New Zealand and South African domestic cricket leagues.
• Day/Night matches: with night-time 3D highlights and match conditions.
• In-Game Help System: help text available with guidance and tips.
• Updated Tournament modes: Updated One Day International and 20 Over World Cup tournaments. Play as any international team that played in the last two World Cups including Afghanistan, Hong Kong, Ireland, Netherlands, Oman, Scotland or the UAE.
• New 3D lighting system.
• User controlled cameras in 3D highlights: choose between active and user-controlled cameras.
• Improved One Day and T20 match engine: combined with revised player form calculation for One Day and T20 games.
• Updated kits: for International teams, NZ and SA domestic teams.
• Historical scenarios: Classic series between England, Sri Lanka and Pakistan.
• Improved interface.
• New database: with improved player ability ratings.
• 58 Game Center Achievements and 12 Game Center Leaderboards