The plugin descriptor /META-INF/plugin.xml tells beaTunes what plugins it needs to instantiate, what version of beaTunes is required and so on. All the important information about your plugin should be right in there. Inside the application it is represented as an instance of the class

As an example, take a look at the keytocomment descriptor (part of the demo plugin available at GitHub ). It's really pretty self-explanatory.


<?xml version="1.0" encoding="UTF-8" ?>
<!-- plugin descriptor for beaTunes Java plugin -->
    <name>Copy key to comment</name>
    <!-- unique id -->
    <!-- version, to be replaced by maven during the build -->
    <!-- meaningful description of what this plugin does -->
    <description>Analysis task that copies the key value to the comment field.</description>
        <name>GNU Lesser General Public License 2.1</name>
    <!-- change notes, also to be displayed in the plugin preferences pane -->
        Adjustments for beaTunes 3:
        - Removed empty editor, as it is now taken care of by beaTunes.
        - Removed explicit persisting of song data, as it is now done implicitly.
        - Removed UI update code, as it is now automatic.

        Minor internal updates. Preparation for beaTunes 3.

        Update for beaTunes 2.1.4.

        Update for beaTunes 2.1.

        First release.
    <!-- organisation that produced this thing -->
        <name>tagtraum industries incorporated</name>
        <email>[email protected]</email>
    <!-- required beaTunes version - please actually fill these in -->

    <!-- list of plugin classes, beaTunes is supposed to instantiate, multiple plugins are allowed -->
    <plugin class="com.beatunes.keytocomment.KeyToComment"/>

BTW: All this information is not only used by beaTunes internally, but also displayed in the plugin preference pane.