Book Image

Eclipse 4 Plug-in Development by Example : Beginner's Guide

By : Dr Alex Blewitt
Book Image

Eclipse 4 Plug-in Development by Example : Beginner's Guide

By: Dr Alex Blewitt

Overview of this book

<p>As a highly extensible platform, Eclipse is used by everyone from independent software developers to NASA. Key to this is Eclipse’s plug-in ecosystem, which allows applications to be developed in a modular architecture and extended through its use of plug-ins and features.<br /><br />"Eclipse 4 Plug-in Development by Example Beginner's Guide" takes the reader through the full journey of plug-in development, starting with an introduction to Eclipse plug-ins, continued through packaging and culminating in automated testing and deployment. The example code provides simple snippets which can be developed and extended to get you going quickly.</p> <p>This book covers basics of plug-in development, creating user interfaces with both SWT and JFace, and interacting with the user and execution of long-running tasks in the background.</p> <p>Example-based tasks such as creating and working with preferences and advanced tasks such as well as working with Eclipse’s files and resources. A specific chapter on the differences between Eclipse 3.x and Eclipse 4.x presents a detailed view of the changes needed by applications and plug-ins upgrading to the new model. Finally, the book concludes on how to package plug-ins into update sites, and build and test them automatically.</p>
Table of Contents (19 chapters)
Eclipse 4 Plug-in Development by Example Beginner's Guide
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Time for action – changing the version numbers


When a new version of the project is released, the plug-in and feature numbers need to be updated. This can be done manually, or by modifying the pom.xml file and MANIFEST.MF version numbers, or by running a tool to do this.

  1. From the parent directory, run the following (all on one line):

    mvn org.eclipse.tycho:tycho-versions-plugin:set-version
      -DnewVersion=1.2.3-SNAPSHOT
  2. The output should say SUCCESS for the parent and SKIPPED for the others:

    [INFO] Reactor Summary:
    [INFO] 
    [INFO] com.packtpub.e4.parent .................. SUCCESS [5.569s]
    [INFO] com.packtpub.e4.clock.ui ................ SKIPPED
    [INFO] com.packtpub.e4.junit.plugin ............ SKIPPED
    [INFO] com.packtpub.e4.feature ................. SKIPPED
    [INFO] com.packtpub.e4.update .................. SKIPPED
  3. Now, run a build to verify that the versions were updated correctly:

    [INFO] Building com.packtpub.e4.parent 1.2.3-SNAPSHOT
    [INFO] Building com.packtpub.e4.clock.ui 1.2.3-SNAPSHOT
    [INFO] Building...