I have project written on Kohana 2.3.4, this project is still active and time to time there is requirement create whole new feature. Because Kohana 2 is no longer supported and whole application stack is quite less I have invest much times possibilities how to upgrade from Kohana 2 to 3. I already know there has been quite a lot of changes and it isn't simple upgrade, it's more like rewrite of application. the directory structure is also different in kohana 3 from kohana 2.
Does anybody have real experience with upgrading Kohana 2 to 3?
Check up this official guide "Upgrading from 2.3.x" for Kohana Framework 3.0 http://kohanaframework.org/3.0/guide/kohana/upgrading
Related
I have the project which is designed and developed on very legacy frameworks. The frameworks which we are currently using are:
jboss-seam-2.2.1.jar
jsf-api-1.2_04-p02.jar
jsf-facelets-1.1.14.jar
jsf-impl-1.2_04-p02.jar
richfaces-impl-3.2.1.GA.jar
These are quite old frameworks, may be around 12 years old or more.
Now, we are planning to upgrade these version to the latest stable version of the frameworks.
The question is, can we directly move from jsf1.2 to jsf 2.3 ? I don't see any documentation or reference for this migration.
Along with JSF upgrade what all are the components we may need to upgrade? Any Direction ?
Thanks in advance!!!
We have SAP Hybris Commerce version 5.1.1 with custom extensions installed. Now we need to upgrade it to newest version 6.2.
My question is: Can we upgrade it to 6.2 and skip all versions between 5.1 and 6.2? Or must it be done by upgrading to 5.2, then to 5.3 and so on?
Yep - 5.1.1 to 6.2 ought to work (I've been working on a project that's done exactly this).
You will probably have to make some changes - watch out for any customisations you've made - it might be worth reading through the release docs to have an idea of what's changed - off the top of my head the structure of add ons is one area that's a bit different between 5.1 and 6.2, but otherwise things should work OK in theory.
Yes you can directly update to 6.2.
It's important to regulary update your hybris version. You should not have so much gap with current version. Indeed it become tougher to migrate your custom code.
Upgrading each minor version in a row is totally useless most of the time. Only do this if you have issues you can't solve while migrating to the target version.
You should take a look at this migration documentation and this guide (it can be used even if it doesn't match your version).
Note that some stuff like promotion are totally different in hybris 6 so you can expect some trouble to migrate everything. Take care of your extensions generated with old template also.
5.5.1 introduces JDK8 and Spring 4, I would not underestimate this change! Depending on the size of your project I would first go for 5.5.1. Also notice the MySQL change for 6.2 (5.6). Don't forget to declare deployment tables in your items.xml. Search for "third-party compatibility" and "release notes" on the wiki. Also try shifting to the backoffice since the hMC is marked as deprecated.
Yes you can migrate directly 6.2.
The time and difficulty depends on your custom code (and how much it respects good practices : naming conventions, usage of service, architecture respect...etc)
You might also consider that HMC is deprecated in 6.2
I am currently working on a project in Orchard. We are looking to wrap up an existing .NET MVC Web application within an Orchard Module. Currently, we are having issues with AutoFac.
The original site was built using AutoFac 3.5, however the latest stable version of Orchard is still running on 3.0. The application requires features introduced in 3.3. If I install 3.0 into the module, the features do not work, if I have 3.5 in the module, it produces a conflict.
Can anybody suggest a way of handling this conflict? Or, is it safe to upgrade AutoFac 3.0 in Orchard and if so how should I perform this without breaking it?
Thanks,
If I may suggest, Orchard 1.9 should be released soon™ and it already has dependency on latest stable Autofac 3.5.2. If you don't want to wait you can grab latest repository from GitHub
https://github.com/OrchardCMS/Orchard/tree/1.9-int
It's perfectly stable in my opinion and I find released 1.8.1 to be much more buggy :D.
Copy the web.config file runtime Node from Existing Module (Lucene or Markdown or like) and add the runtime node on conflicts Module Web.Config file. After Compile then clear the Conflict
I like Jelly ORM and I want to use it with Kohana 3.2. However, I'm receiving different errors as I try its various methods and actions.
I see the last update to Jelly ORM was more than year ago on github.
Should we say "Goodbye" to it?
The original author of Jelly stopped active development before Kohana 3.1 was released. From that point, someone else forked Jelly and upgraded the unstable branch to Kohana 3.1. I don't know the current state of this fork. But upgrading that one for Kohana 3.2 shouldn't be too much work.
This should be working now: http://forum.kohanaframework.org/discussion/9833/jelly-for-kohana-3.2-auth-driver
The latest stable release of Mono right now is 2.4.2.3. Does subsonic 3 work with it? I know Mono isn't compatible with all .net 3.5 features yet, but I'm presuming compatibility depends on which specific language features of .net 3.5 Subsonic uses. Does anyone know for a fact whether it's compatible?
Its compatible - just remember to use an actual version of MySQL connector, if planning to use MySQL.
And there is an Error in current SubSonic (see Issue 111). Change IsDbNull to IsDBNull in SubSonic.Core/Linq/Structure/ExecutionBuilder.cs and recompile.
That did it for me with Mono 2.6 and MySQL-connector 6.2.2
But I didnt't test anything but simple save and read queries.
from the looks of the code not everything seems to be full hilt 3.5 so i would cast an opinion that it will be just fine, i have been using 3.0.0.3 and resharper comes up with tones of comments about how it can be changed and upgraded.
but it takes less than 5 mins or so to test, so i would go ahead if i was you, you dont really have much to loose other than 5-10 mins.
hope this helps