Hi Eloy, I guess this is not buckminster related, though. Have you tried to set
org.eclipse.equinox.p2.roaming=true when creating the product zip? As I remember this prevents hardcoded install locations. Regards Thomas 2011/8/19 Eloy Gomez <[email protected]> > Hi all! > > I have a eclipse based product build with buckminster following this > tutorial: > http://www.ralfebert.de/blog/eclipsercp/rcp_builds/ > > This produce .zip products with native lanunchers and p2 enabled, but > when try to install new plugins, ever write the configuration on the > buckminster install folder. > > This is the scenario: > First, export my product under this > directory /tmp/buckminster.out/my_feature/product.zip > > Unzip the product under /home/user/product > > Try to install a new plugin, then P2 write the configuration > in /tmp/buckminster.out/my_feature/product/product.ini. Features and > plugins are installed > into /tmp/buckminster.out/my_feature/product/features > and /tmp/buckminster.out/my_feature/product/plugins > > in > p2/org.eclipse.equinox.p2.engine/profileRegistry/MyProductProfile.profile/ > there are profiles.. Both have the value of > org.eclipse.equinox.p2.installFolder set to the buckminster export > directory: /tmp/buckminster.out/my_feature/product/ > > > When export my product inside Eclipse (open product file, then click on > Export product) works fine.. > > How can I solve this??? > > Thanks!! > > > -- > Indeos Consultoria > Tel: 966787431 > www.indeos.es > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev >
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
