Community
Participate
Working Groups
Build Identifier: Current documentation lacks any information about -roaming director's switch. It's also not included in provided build\product.ant file. Reproducible: Always
So, before writing any documentation about this, should the ant tasks use roaming by default? (What negative effects could that have?)
I'm no expert at this, but isn't the only effect of the -roaming parameter to decide if some p2 configuration settings are written during the first startup, or directly after the product creation? If -roaming is not passed, the director assumes that the given destination is the final location of the product and therefore the configuration is written immediatly. This makes sense in case of the buckminster headless setup for example since you create the product already in its final destination. If you pass -roaming, p2 will write this information as soon as you start the product for the first time. In case of a build process you most likely want to deliver the build output to somewhere so -roaming should be the default setting since you can't know what the final location of your artifact will be. The only negative effect 'should' be that the first startup is a little slower than without the -roaming since p2 has to compute and persist some settings. +1 for -roaming in the ant task
I don't know exactly either, when I looked at this, it seemed like the roaming install uses more complicated relative URLs, but I don't know if that is the only difference. I think the install is still roaming after install and startup. But I could be wrong.
The installation is definitely still roaming after first startup. And as for the buckminster headless setup, -roaming is my best friend there, too. That way, I can build my setup and run a few test materializations before copying it over to our Hudson.
+1 for "-roaming" in the ant task I have Hudson-Buckminster setup to create an update site and a RCP product, which has the p2 Updater built in. Without the roaming switch the Online Update fails, as the updated plugins get installed in the same ABSOLUTE path they got built/deployed in on the built server. With "-roaming" it seems to work as expected.
I have run into the same problem as Frank (comment #5) and spent days trying to figure out whats going wrong with the P2 update... please add roaming to the mailapp product.ant script.
Use of -roaming has been added to the documentation including a reference to this issue. It will appear in the first bucky book version after 0.8. The underlying issue (not setting -roaming in the example) should also be fixed, so leaving this issue open.
