Make your upgrade step just apply the profile it will install thé new dependencies. Le 23 avr. 2013 13:24, "Jochen Dekeyser" <[email protected]> a écrit :
> I want to clearify my question, I don't think my previous question is > completly clear: > Suppose I have an add-on with metadata.xml > > <?xml version="1.0"?> > <metadata> > <version>1</version> > </metadata> > > Now I want to upgrade my add-on and metadata.xml to: > > <?xml version="1.0"?> > <metadata> > <version>2</version> > <dependencies> > <dependency>profile-mydependency:default</dependency> > </dependencies> > </metadata> > > And I want to create an upgrade step which automatically installs > profile-mydependency:default when I upgrade from version 1 to version 2... > > What is the best practice to do this? > > > > -- > View this message in context: > http://plone.293351.n2.nabble.com/Best-practice-to-install-additional-dependency-profile-in-upgradestep-tp7564667p7564674.html > Sent from the Product Developers mailing list archive at Nabble.com. > _______________________________________________ > Product-Developers mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-product-developers >
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
