Description

This test case tests whether local building of a Fedora package works correctly when using Fedora Packager for Eclipse.

Setup

Boot into the machine/VM you wish to test
Ensure the eclipse-fedorapackager-0.2.1-1.fc16 package IS installed. Install it via yum install eclipse-fedorapackager-0.2.1-1.fc16.

Open Eclipse and use a new workspace. eclipse -data test_day_20111013_fpe_local_build
Press Ctrl+Alt+F I to open the import wizard. Alternatively press Ctrl+3 and start typing "Projects from Fedora Git", then press return.
Enter the package name of a package you maintain or use package ed. Make sure to clone anonymously by selecting the appropriate checkbox and click "Finish".
The package you've just cloned should show up in your workspace.
Expand the project you've cloned into your workspace and double-click the .spec file in it. The .spec file should open in the editor.
Right-click in the .spec file and select "Fedora Packager" => "Build for Local Architecture", alternatively press Ctrl+Alt+F L with the .spec file open in the Eclipse editor view. You may have to install all packages which are required for building the package at hand (look for BuildRequire listings in the .spec file).
This will trigger a local RPM build of your cloned package using the sources as listed in the sources file (for the current branch, usually master, which is mapped to rawhide).
Go to the "Git Repositories" view, expand the repository of the package your are currently working on, expand "Branches", then "Local", then double-click on "f15". This should checkout the "f15" branch of your local Git clone.
Repeat steps 6-7. This should produce RPMs for Fedora 15.

Build is correctly triggered and relevant output is printed to the Eclipse console.
After the build has been finished successfully, a folder <ARCH> is created in the project of the package you've just built. For example if your package was noarch, you should see a noarch folder which contains all binary RPM files for the current distribution which the .spec file produces. The distribution is determined by the currently checked out Git branch. For example if the current branch was f15 you should see .f15 in the file names of the produced binary RPMs.