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 – creating a bug


Reporting bugs in Eclipse is a simple way of getting involved. These steps will use the example of the title case of SWT as an example, although this is not likely to be accepted as a real bug!

  1. Open a web browser and go to https://bugs.eclipse.org in order to create a bug. It may be necessary to log into the account if the option is not set. It may be beneficial to uncheck the Restrict this login session to this IP address, as otherwise if the computer's IP address changes, then it will be necessary to log in again.

  2. Once logged in, a File a Bug button will be displayed; alternatively the new link at the top of the page will allow a bug to be created.

  3. The Eclipse bug wizard will show the steps necessary to create a bug. The form will guess the operating system and hardware type based on the browser information, but for non-OS-specific bugs such as documentation, these should be set to All.

  4. The bugs are categorized into different areas; Technology contains general...