[kepler-users] trouble moving kar files between kepler instances

[Derik Barseghian]

Hi Frank,

Can you tell how you're trying to use the kars, and the error you're seeing when trying to use these trunk-reporting actor kars in your production kepler?

Also, I'm unclear which suite(s) your production environment is running - reporting 2.1 is the only official release of reporting at this point, and it relies on kepler-2.1, so kepler-2.2 shouldn't be involved. On your production kepler, could you tell me what Tools=>Module Manager says your Current Suite is? If you're in reporting-2.1, this should show *workflow-run-manager-2.1. You should be able to use reporting-2.1 to open workflow kars saved while running reporting  trunk. However you're trying to create actor kars, maybe there are some problems with that. I'll look at the issue in more depth after I get your answers to the above.

Thanks,
Derik


On Mar 29, 2011, at 1:35 PM, Frank White wrote:

> Hello All:
> I'm having trouble moving actors (kar files) that I developed in one instance of Kepler in my development environment to run in another instance of Kepler in my 'production' environment.  The dev instance was built from the latest kepler trunk, while the production instance was built from the Kepler 2.2 suite. Both instances load the 'reporting suite', and so should have identical modules.
> 
> The most notable difference I'm seeing is in the dependencies list in the kar file manifests: kars built on the dev instance list just the dependent module names without version numbers, whereas kars built on 2.2 have the full module name and version number.
> 
> Does anyone know a good way to transfer actor kar files between instances?  Appreciate the help.
> 
> Cheers!
> Frank White
> fwhite at optensity.com
> 
> -- 
> Frank White
> fwhite at optensity.com
> 781-771-2798
> 
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users