![]() We’ve successfully set up the Forge shell! Let’s quit out for now by typing exit then pressing enter and we’ll go through the steps to install the JBoss Tools Forge plugin in Eclipse.Īt the time of writing I’m using the latest release version of Eclipse, Kepler SR1. When you start forge, it will attempt to install the latest released versions, however in our case we want to install the artifacts that we just built ourselves, so to do that we must first run forge -i core,2.0.1-SNAPSHOT - alternatively just use the offline distribution and save yourself a lot of trouble.)įorge will download a bunch of stuff and then prompt you to confirm the installation, so select Y and press Enter again.Įventually the installation will complete and you’ll be sitting at the Forge command prompt:įrom here you can press the tab key to see the available commands: (Note: If you didn’t install the offline distribution, you’ll be prompted to install the core addons. When that’s done, run the forge command from a command prompt. ![]() This is an OS-specific step so it’s up to you to complete this by yourself. Once that’s done, you need to create a FORGE_HOME environment variable pointing to this directory, and add the $FORGE_HOME/bin directory to your path (this will allow you to execute the forge shell from anywhere). ![]() I generally like to install tools like this into a dedicated apps folder, and if you’re on a *nix based OS I recommend creating a symbolic link also: For now, I recommend you use the offline distribution, so extract it to its own folder somewhere. You have a choice here, you can either use the (smaller) distribution zip which doesn’t come pre-packaged with all of the core addons, or you can use the larger offline distribution which has the addons packaged also. Open the forge-core/dist/target directory where you’ll find some zip files containing the Forge distribution: Once everything has built successfully, it’s time to install Forge. If all goes well you’ll get a BUILD SUCCESS message at the end:Ĭontinue by building the other three projects ( furnace-cdi, forge-code and jbosstools-forge) in order using the same Maven command. You’ll need Maven 3.1 or higher for this step: Once you have them all build each of them using Maven, making sure to skip the tests. I strongly recommend that you work with the latest trunk of Forge, so fire up your terminal window and start by cloning the following repositories from GitHub: Also, while the addon itself won’t actually do that much, we’ll try to cover all the basics which will hopefully provide the solid foundation you need to be able to implement more complex features. I had the privilege today of receiving some expert tutelage on Forge Addon development in Eclipse from the Forge Team’s George Gastaldi, and I was so impressed by how easy it was that I’m going to describe the process step by step so that you too can experience the pleasure of writing a Forge addon! This guide is written from the perspective of a complete Forge noob, so you can rest assured that it has made a very strong attempt to capture all the little important details.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |