How to make a JAR file Linux executable ExampleEvery Java programmer knows or should known that it is possible to create a runnable Java package archive JAR, so that in order to launch an application it is enough to specify the jar file name on the Java interpreter command line along with the jar parameter. For example java jar helloworld. There are plenty of tutorials showing how to implement this feature using Ant, Maven, Eclipse, Netbens, etc. Anyway in its basic form, it just requires to add a MANIFEST. MF file to the jar package. The manifest must contain an entry Main Class that specifies which is the class defining the main method for your application. WBikK.jpg' alt='Execute Jar File Using Ant' title='Execute Jar File Using Ant' />For example javac Hello. World. java. echo Main Class Hello. World MANIFEST. MF. MANIFEST. MF helloworld. Hello. World. class But this still requires your users to invoke the Java interpreter with the jar option. There are many reasons why it would be preferable to have your app runnable by simply invoking it on the terminal shell like any other command. Execute Jar File Using Ant' title='Execute Jar File Using Ant' />Installing Apache Ant Getting Apache Ant The Short Story. To get up and running with the binary edition of Ant quickly, follow these steps Make sure you have a Java. Here comes the protip This technique it is based on the ability to append a generic binary payload to a Linux shell script. Read more about this here http www. Taking advantage of this possibility the trick is just to embed a runnable jar file into a Bash script file. The script when executed will launch the Java interpreter specifying itself as the jar to run. Too complex Much more easier to do in practice, than to explain Lets say that you have a runnable jar named helloworld. Copy the Bash script below to a file named stub. MYSELFwhich 0 2 devnull. MYSELF. 0. if test n JAVAHOME then. JAVAHOMEbinjava. MYSELF. Than append the jar file to the saved script and grant the execute permission to the file resulting with the following command cat stub. I am using seleniumserverstandalone3. Firefox 31. String driverPath UsersanandmahajanDesktop public void launchBrowser. Static code analysis tool that analyses Java bytecode and detects a wide range of problems. Available as standalone application or as plugin for common Java IDEs. Thats all Now you can execute the app just typing helloworld. The script is smart enough to pass any command line parameters to the Java application transparently. Cool Isnt it In the case your are a Windows guy, obviously this will not work except you will run a Linux compatibility layer like Cygwin. Anyway exist tools that are able to wrap a Java application into a native Windows. See for example http launch. Execute Jar File Using Ant' title='Execute Jar File Using Ant' />TFS build automation for a Java project using Ant. In a previous article, I walked through the process of installing and using Team Explorer Everywhere on an Eclipse environment. That way, you can use TFS for your Java development. In this article, I will cover the process of how you can use the Team Foundation Build Automation to automate your Java builds using Ant. Ill guide you through all the necessary steps and give you some personal experiences. First of all, you need to have Team Explorer Everywhere installed more about that in my previous post. If you have this, youre ready to go. Execute Jar File Using Ant' title='Execute Jar File Using Ant' />Getting started with Java and Ant. To start, let me explain you what Ant is and how you can use it. Apache Ant is a software tool for automating software build processes. It is similar to Make but is implemented using the Java language, requires the Java platform, and is best suited to building Java projects. Ant stands for Another neat tool and was released at first in 2. The Ant build definitions are declared in a build. The root node of a build. This target will be executed when you build your project. Workbench User Guide Eclipse platform overview Getting started Basic tutorial The Workbench Editors and views Editors Views. First, its kind of weird, to see you run java jar app and not java jar app. Second, to make a jar executable. METAINF. Selenium Grid is used to speed up the execution by using multiple machines multiple browsers with different versions, and browsers running on different operating. The child nodes of a project are those target definitions. You can define as many targets as you want. For example clean, compile, jar. Each target can have its dependencies. You can define that the jar target depends on the clean and compile target. That way, you have a sequence of executing. Let me give you a really basic example. When you use Eclipse, you can use the Ant window to visualize the Targets of your build. Link your build. xml file using the add build files button Using this window, you can also execute a specific Target by double clicking on it. Be sure that you do a check in of your build. Create a build definition. Now you have Ant up and running, we can define our TFS build definition. This build definition will take care of the build process on our TFS build controller. If you want to learn more about build controllers and build agents on TFS, take a look at this article. Open the Team Foundation Server Explorer in Eclipse using the Team Foundation Server Explorer perspective. Select Builds node, right click and select New Build Definition2. In the new window, the first thing you have to do is provide a build definition name and a description. The next step is to define the build trigger. Choose the option that suits you the best. In my case, I selected a Continuous Integration Build. The following step is the definition of your working folders. This is the mapping that the build server will use. If you defined a custom workspace mapping on your local machine, you can also copy this using the Copy Existing Workspace button. Select your build controller and the place where to output your files. Note that even on Linux, if you use a network location, use location and not smb which you would normally use on a linux machine to access a Windows share. Thats because the build controller is running on a windows machine, and this controller uses the network path you define there. On the project file section, you can define which build you want to use. Click on the Create button to start a new wizard. The first step in this wizard is to select which build file you currently have. In our case this is an Ant build file. Select this an click next. The next step is to select your build. Click finish to close this wizard. As you can see now, the wizard tells you that there was a MSBuild project file found. That file was automatically created by the previous wizard. Note that this file is located in a folder called Team. Build. Types. If you want to understand whats in that TFSBuild. The last step is to define your Retention policy. There you can select some numbers of how many files are kept when a build succeeds, fails. Click Ok to create your Build Definition. You Should now see your new build definition in the list. Build server changes. To summarize We have a Java project, an Ant build. TFS build definition based on the Ant build file. The next step is to prepare our TFS Build server so it will be able to build Java projects based on AntMaven. For that, you will need the Team Foundation Server Build Extensions Power Tools. Cara Crack Corel Video Studio X5 Crack. They can be download here. This extensions provide the ability to execute Ant or Maven 2 builds from Team Foundation Server and publish the results of the build along with any associated JUnit test results back to TFS. After you have installed this on your build server, be sure that you have the correct JDK and Apache Ant installed. Next thing you may not forget is set the correct environment variables to your build system. I spend quite a while looking for the correct one, so here they are Add a system variable ANTHOME with value C Program Files. Win. Ant or where Ant is installed. Next add a system variable JAVAHOME with value C Program Files. Javajdk. 1. 6. 02. The last step is to edit your system variable called Path. At the end of this value it should already contain a bunch of other settings you add JAVAHOMEbin ANTHOMEbin. Now youre ready to go. The build server can now execute Ant builds. Ant build usage with TFSThe nice thing about using Ant with TFS is that the TFS build will provide some extra parameters that can be used in your build. For example you have Binaries. Root, Build. Definition. Name, Build. Directory, You can use this parameters in your Ant build definition. Ill combine the previous explanation with the fact that you also have conditional parameters in your Ant build file. What I mean is that you can declare variables, depending on the fact that the variable is or isnt defined. For example, if you run your Ant build inside your Eclipse, you have no Binaries. Root variable available. Thats because this is provided, additionally, by our TFS build script. What we  can do is the following lt condition propertydir. Binaries. Root lt isset propertyBinaries. Root lt condition lt property namedir. So if the Binaries. Root variable exists, then use it, otherwise use the basedir instead. That way, you can create your Ant build so that it does run local, but also on the build server. Run your build. Now you have all the parts completed, its time to execute your build. Using your Team Explorer in Eclipse, right click on your build definition and click Queue new build or do a code check in if you defined a CI build. Now you should see the build running in the Build Explorer Window. Double click on the build to see the results. You also have a log, containing the output of the Ant build. If you go to the drop folder, you should see your output files. Now its up to you to change your Ant build file, and play with some targets. In a next post, I will explain how you can define JUnit tests in your Java application, and also link the results to your TFS build, and even watch the results in Visual Studio.