Book Image

Eclipse Plug-in Development Beginner's Guide - Second Edition

By : Alex Blewitt
Book Image

Eclipse Plug-in Development Beginner's Guide - Second Edition

By: Alex Blewitt

Overview of this book

Eclipse is used by everyone from indie devs to NASA engineers. Its popularity is underpinned by its impressive plug-in ecosystem, which allows it to be extended to meet the needs of whoever is using it. This book shows you how to take full advantage of the Eclipse IDE by building your own useful plug-ins from start to finish. Taking you through the complete process of plug-in development, from packaging to automated testing and deployment, this book is a direct route to quicker, cleaner Java development. It may be for beginners, but we're confident that you'll develop new skills quickly. Pretty soon you'll feel like an expert, in complete control of your IDE. Don't let Eclipse define you - extend it with the plug-ins you need today for smarter, happier, and more effective development.
Table of Contents (24 chapters)
Eclipse Plug-in Development Beginner's Guide Second Edition
Credits
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

Time for action – setting job properties


It is possible to associate arbitrary properties with a Job, which can be used to present its progress in different ways. For example, by specifying a command, it's possible to click on a running job and then execute something in the user interface, such as a detailed job description. Job properties are set with setProperty and can include any key/value combination. The keys use a QualifiedName, which is like a pair of strings for namespace/value. In the case of the progress view, there is an IProgressConstants2 interface that defines what values can be set, including COMMAND_PROPERTY, which can be used to associate a command with a Job.

  1. Open the HelloHandler and go to the execute method. Just before the Job is scheduled, acquire the Command from the ICommandService and then stamp it on the job as a property. This will require adding an argument into the method signature and adding org.eclipse.core.commands as a dependent bundle:

    public void execute...