This session will explain a real world derived use case, where we use the new trigger system (since 0.13) in Eclipse Package Drone to restrict the upload to artifacts which don't already exist and also prevent uploading artifacts with the same version but a different content. Of course there will be a short introduction to Package Drone, and some other interesting use cases will also be covered. With the titulary use case, there will also be a short introduction to the RPM and DEB builder library. Last but not least, there will be an outlook what will probably come in the next versions.
Eclipse Package Drone™ is a software artifact repository. A system which stores software packages (like JAR files, Debian Packages, …), extracts information, transforms these and provide access via different repository interfaces. Its initial focus was on providing a repository system for the different repository formats (like P2, Maven, OBR and OSGi R5) with a focus on OSGi. Over the time the system was enhanced to allow pluggable adapters for other content types and repository adapters.