[tycho-user] p2-installable-unit in update site builds?

[Jed Anderson <jed@xxxxxxxxxxxx>]

Hi,

I've found this new demo which outlines using the new p2-installable-unit packaging type in tycho.  Cool, this is an improvement over the p2.inf!

http://wiki.eclipse.org/Tycho/Demo_Projects/RCP_Application

I have been trying to use p2-installable-unit it in my build that creates an update site.  Is this packaging intended to work outside of RCP product builds?

When I try it, I don't see the metadata nor the binary artifact created in my update site. 

I have mimicked the poms & p2iu.xml files in the example.  The p2artifacts.xml, p2content.xml, and artifact zip for my IU do get created in my local target directory.  Is there a trick to getting these to get picked up by my eclipse-repository pom?

Some things I have noticed that might be part of the issue:

1. The generated artifact zip's version ends in -SNAPSHOT, e.g. 1.0.0-SNAPSHOT.  I would have expected SNAPSHOT to get replaced with the build qualifier.

2. The filename of the zip is <id>-<version>.zip whereas the standard p2 binary format is <id>_<version>.  Maybe this gets mapped to the right binary name during update site creation?  If not, is there a property to configure the artifact name?

Any pointers would be greatly appreciated!

Cheers,

jkca