09-10-2013 05:30 PM - edited 09-10-2013 05:32 PM
Solved! Go to Solution.
09-11-2013 02:59 AM
Had a similar issue - but in reverse - adding a BB10 release to a current playbook release.
Here is how I got round it - should work in reverse I think.
1. open the playbook .bar file
2. open the MANIFEST.MF in the META-INF folder
3. get the package name ( here is an example from one of my packages.
4. change the bb10 config file to include the package name :-
Hope this helps