Unlocking a Designer package you created

When you are working with Designer and you create new packages, you can only modify the package in the project that created the package. Luckily, Designer allows you to use subversion, so you can share the project, resulting in all connected designer instances to share the same project, and thus being able to 'own' the same packages.

But what if you do not have subversion, or you are at a client that does not allow access to your subversion repository? In this case, you can import the custom packages, but you are unable to modify the content of the package or create a new version of this package. You can only copy a specific version to a new package, breaking your package structure.

This Designer extension allows you to mark a package (any package!) as 'Local', thus allowing you to create a new version of your package or add new content to the package.

Note: only use this on packages that you are actually owning. If not, the vendor of the package might release a conflicting version (and then you'll have a mess to clean up).


  1. Change the extentions of the attached file to '.jar' (Cool tools does not allow files with a jar extention) and copy the file to Designers plugin folder.

  • (Re)start designer, making sure your project is in 'developer' mode.

  • If you right-click on a locked package, you should have an additional menu item: ”Mark as 'Local'”.

  • Selecting this menu item, will request a confirmation of your action. Pressing 'OK' will unlock the package, allowing you to create a new version.

Note: this plugin also adds a log viewer to you packages: right click on any package and select “View changelog”. This is a log of the package as defined by the actions created by Novell.

More information:

See the product website for this and other cool tools.

Version history:

  • 1.0.1, 16-APR-2016:

    • Changed the warning text in agreement with NetIQ

  • Added about.html

  • 1.0.0, 05-OCT-2011:

    • Initial release, contains the package unlocker and a package changelog viewer



How To-Best Practice
Comment List