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 – adding logging


The OSGi platform defines a LogService which allows messages to be logged to a central collector. In the E4 platform, an instance of LogService is available as part of the platform, routing error messages through to the console.

  1. Open the Hello class and add a private field LogService logService.

  2. Add an @Inject annotation to the LogService field.

  3. In the create method, add a call to the log service.

  4. The Hello class will look like:

    import javax.inject.Inject;
    import org.osgi.service.log.LogService;
    public class Hello {
      @Inject
      private LogService logService;
      @PostConstruct
      public void create(Composite parent) {
        label = new Label(parent, SWT.NONE);
        label.setText("Hello");
        logService.log(LogService.LOG_ERROR, "Hello");
      }
      ...
    }
  5. Run the application, and a log message will be printed out to the console of the host Eclipse:

    !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-06-02 13:36:42.381
    !MESSAGE Hello
    

What just happened?

The E4 runtime infrastructure...