|RE: [p2-dev] update site from the product build|
Thanks Andrew and Ian,
I did double check and made sure I use newer version of the repository, and the build id portion in the product ID was newer.
I enabled all the P2 trace options in the “.options” file:
I see P2 pounding the update site and produced a lot of “Unexpected attribute for element license: url="" messages and then quietly exited without any error.
Besides the above trace options is there any other way I can ask P2 to produce more verbose debug information, e.g. what it finds and what it compares with?
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Niefer
The product build generates a “buildRepo” directory. In that directory there are “binary”, “feature” and “plugins” folder, and “content.xml” and “artifacts.xml” file.
We have daily builds. Each build increase the build qualifier in the product ID (e.g. 188.8.131.5290930 to 184.108.40.20691001). The main features and sub-features also has build qualifier increased daily.
I run build 220.127.116.1190930 and add a new update site URL pointing to the “buildRepo” from build 18.104.22.16891001. However when I run “Check for update” I get “There is nothing to update” message.
Is there anything wrong with my config? Can I use the “buildRepo” directly as update site?