I need to upgrade from NHibernate 1.2.x to the latest version. Can someone help me out by either pointing me into the right direction, explain to me what I need to do, or just shoot me for using 1.2 when it's almost 2013.
Please.
Easy Answer: Have you tried just dropping in the latest version? 3.x should be somewhat compatible with what you have.
Hard Answer: Download Fluent NHibernate and get ready for some fun learning. It all depends on why you feel the need to upgrade.
The release notes in the download list know and possible breaking changes. It may be worth looking through. Other than that, I would suggest just dropping the new files in and see what happens.
Related
in the current Documentation of Optaplanner (7.40.0.Final) it says:
"The easiest way to explain the score during development is to print the return value of explainScore()"
When I create a scoreManager it doesn't have the method explainScore()
How do I get the explanation of the score in the Terminal? Where do I have to call the scoreManager?
I am working with Quarkus and my problem is very similar to the TimeTabling Problem.
Best regards and thank you in advance
Justin
Are you using the version coming with the Quarkus Platform BOM? Because in this case, it's 7.39.0.Final and that could explain your issue.
You can define the version yourself and upgrade to 7.40.0.Final. It might work, Geoffrey would be able to confirm.
He will also be able to tell you if he plans to upgrade Quarkus to 7.40.0.Final for 1.7.
That method was introduce recently. OptaPlanner 7.40.0.Final, the same version as the docs you're reading, definitely has it:
https://github.com/kiegroup/optaplanner/blob/7.40.0.Final/optaplanner-core/src/main/java/org/optaplanner/core/api/score/ScoreManager.java#L81
Now when we are required to update some modules for 64 bit support, I just found that one of our most important modules are nowhere to be found anymore.
Ti.healthkit was found previously on: https://labs.appcelerator.com/project/55c3c788e014044625e9b2a1/HealthKit-Module
Does anyone know where to find it now? Really need to somehow make sure it's upgradeable to support the latest titanium version.
Thanks
we are planning to migrate our codebase from xI50 to xI52. Could anyone please let me know, how xI52 is different from XI50 ?I am just tryingt to figure out what kind of changes will need to be done to our existing codebase on xI50 to make it compatible on xI52?
Also, I have below two questions:
1) Is Xi52 the best hardware to which we should migrate from Xi50? What are the advantage of Xi52 from others?
2) What are the best practices to migrate the configuration from Xi50 to Xi52?
Regards,
Rahul
Good question Rahul!
As a rule of thumb, the compability of the codebase is essentially an aspect of the running firmware, not the model in itself.
So, figure out the firmware version of your XI50 and your target firmware, which probably is the latest. If you upgrade to the same firmware version (such as version 5), there should be no issues.
Here is a list of all firmwares.
http://www-01.ibm.com/support/docview.wss?uid=swg21237631
The release notes to look for information in each firmware, so go through the list (you may have to aggregate through several firmwares, such as 4.x to 5.x, 5.x to 6.x).
Sometimes, you have to look into individual technotes for info.
In general, DP contains compability rather well, and breaking changes resides mainly in details.
http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/index.jsp?topic=%2Fcom.ibm.dp.xi.doc%2FrelnotesXI.html
http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/index.jsp?topic=%2Fcom.ibm.dp.xi.doc%2FrelnotesXI.html
I'm getting ready to deploy the first release of our software, version 1.0. Once it's out to our customer, inevitably, some bugs will be found. When I fix those bugs though, I'm not sure what "best practice" is for versioning it. When I release the fixes, would that be an entirely new version (in maven), such as 1.01 (or whatever the increment is, 1.1 for example)? Or would it still be 1.0 with some sort of classifier (maybe a date tag)?
Thanks,
Jeff
Wikipedia has a surprisingly thorough discussion of software versioning. It covers all the major points and discusses most of the approaches I've seen.
(In your specific case I'd go with 1.0.1 which would generally be regarded as "an update to 1.0 with no significant feature additions")
You have to change the number in order for maven clients to recognize a newer version in the repository. The change is up to you. I'm sure there's a best practice document somewhere but my company dictates the numbers we use so I've never looked for one.
I use Intellij Idea 7 for Java dev. My dev is 'limited' to all J2SE features plus light JSP, Servlets, and super light usage of JPA. No J2EE, no massive use of random frameworks, etc.
Is it worth upgrading to ver 8? "Worth it" to me means better "core functionality" in terms of speed (ESPECIALLY startup speed), memory utilization (seems like it starts having serious problems with four or more projects open), and auto bug-finding.
More frameworks supported and more languages supported (other than perhaps Haskell and C++), and more refactorings don't interest me at this time.
A while back, I installed a preview version of 8 and it seemed -exactly- the same as 7, as far as my needs were concerned.
Anyone loving the upgrade to 8, and if so, why?
Thanks
It also seems to be easier to configure a new project over top of a complex collection of existing code.
For example, something that you would naturally configure into 5 or more modules.
There is a really beautiful go to/create test wizard that is bound to ctrl-shift-T. Worth the upgrade by itself
The best way to tell is to check out the list of new features and decide for yourself. I haven't discovered any single feature so far that by itself is worth upgrading - the simplified UML view is quite nice, as is the improved Maven integration. The UI feels a bit more streamlined and faster. It seems like most of the attention has gone into non-Java features like better Flex support (which I am really thankful for as I don't like FlexBuilder but I haven't had a chance to use yet).
IntelliJ 8 has a configure plugins feature that allows you to disable plugins with dependencies. Nothing trial and error couldn't replicate, but it is nice.
Startup is only marginally slower. But indexing once opened is a lot faster than before, even unnoticeable for most projects, except after a commit to Subversion. It seems a commit to subversion triggers the indexing twice.
I am working on the Diana-EAP build - but 8 has git integration built in. The EAP has better git integration than the 8.0.1 release - it looks like that is something they are really focusing on.
Definitely not! Seems that the variables defined in our custom taglibs are no longer able to be used in the jsp (worked in 7.0.4). All red. No auto complete.
Oh, and the new settings menu is horrendous!
Some benefits of IntelliJ IDEA 8:
IDEA 8 supports Subversion 1.5 new functionality - e.g. merge tracking, which may be useful especially if your team (like ours) uses a lot of development branches and thus merging is frequent.
One detail I appreciated about IDEA 8: As you probably know, IDEA has had changelists for pretty long now, built on top of any underlying version control system - this is a really useful feature. So, now that Subversion itself supports changeslists, IDEA's changelist implementation has been changed so that it is perfectly compatible with Subversion's native changeslists. (For example, you'll be able to work with any changelists created in IDEA also when using svn command line tools directly.)
Edit: in your case, perhaps it is not worthwhile to upgrade. For me, at least, startup and file indexing seems to be somewhat slower in 8 than 7. [But for me personally the upgrade was definitely worth it, because it solved a long-standing VCS problem with IDEA 7 - it could hang "waiting for VCS sync to finish" for an hour or whatever after hitting Ctrl-K.]