Working on a uP3 upgrade for JHU, I discovered that there's a "gotcha" when you export you're channel-types from a 2.6 portal and import them into a 3.0 portal: the Portlet Adaptor class has changed. The default data set for uP3 correctly references the new one, but if you export everything from your old portal, your channel-type for Portlets will specify the old adaptor class (which, of course, is perfectly correct for your old portal).

I will attach a patch that does 3 things:
  - (1) adds a import-channel-type_v3-0.crn script that does everything the v2-6 script did, plus it checks to be sure the channel class you specify is present in the classpath
  - (2) updates the import-channel-type_v2-6.crn script to forward execution the v3-0 script, but first check to see if the old portlet adaptor class is specified; if it *is* specified, it changes the class to the new portlet adaptor
  - (3) updates the export-channel-type script to specify the import-channel-type_v3-0.crn script as the native end point for importing newly exported channel types; in other words, channel-types exported from uP3 won't go through the v2-6 script and (consequently) won't get the check for the old portlet adaptor class (they don't need it).