[Product-Developers] Questions regarding GS upgradeStep

[Francois Barriere]

Hello,

   In my product I have added new lines to the diff_tool.xml file
(under profiles/default), plus some fixes. I then registered an
upgradeStep with the following configure.zcml snippet:

	<gs:upgradeStep
		title="Upgrade ATMEL.policy product"
		description="ATMEL.policy product migration/upgrade steps"
		source="*"
		destination="0.3"
		handler=".migrations.migration_to_0_3"
		sortkey="1"
		profile="ATMEL.policy:default"/> 

The source is "*" as there was no previous upgrade step, I have a handler that
does various fixes using Python code and defined the profile.

When upgrading the Python code is executed by the regular import steps are
not (the changes in profles/default/diff_tool.xml) are not reflected.
I thought the upgrade would re-run the import steps of the profile...

Am I wrong? Should I force the import step from my Python code?
In this case, what is the use of the "profile" attibute of the
upgradeStep?

Francois.

-- 
   Francois BARRIERE                          ATMEL
                                              Zone Industrielle
   Tel: (33) 0 442 53 61 98                   13106 ROUSSET
E-Mail: francois.barriere at atmel.com           FRANCE
                 ---------------------------------
Everyone knows that debugging is twice as hard as writing a program 
in the first place. So if you're as clever as you can be when you write it, 
how will you ever debug it? (Brian Kernighan)
                 ---------------------------------