According to groovy-eclipse plug-in website, groovy-eclipse plug-in supports certain groovy versions, 1.8, 2.0 and 2.1. This seemed a bit restrictive to me. What am I supposed to do if I work with groovy 1.9 or 1.7?
Perhaps the answer is that if you worked with Eclipse or GGTS before, then that couldn't happen; I suspect they never supported 1.9 or 1.7.
What is your concern? If you're worried that you might start off with 2.1 and have it not supported in future, then don't worry. If you're expecting to use some bizarre compiler feature that only worked in 1.9, then edit with the eclipse plugin for any version, and run Groovy (or Grails) from the command line with the right configuration.
Hope this helps...
Charles
Groovy-Eclipse supports the last couple of versions of groovy so we don't get into a maintenance headache. There is no Groovy 1.9 so we support right now 2.2/2.1/2.0/1.8 - we dropped 1.7. If you want to use 1.7 you would use an older version of groovy-eclipse that supported it. See version 2.8.0: http://groovy.codehaus.org/Groovy-Eclipse+2.8.0+New+and+Noteworthy - on that page you can download an update site archive that will give you groovy-eclipse and groovy 1.7.10
Related
What is the best support for groovy in Eclipse. Are there any plugins you could recommend. I tried Greclipse Plugin, but it seems not full compatible with STS 3.9.2 ...
Ah, it seemed I took an old link of Greclipse. STS3.9.2 seems to be compatible with http://dist.springsource.org/snapshot/GRECLIPSE/e4.8/
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
On the swift website you have several options / versions to choose from, but some of the packages don't seem to include swift-build, what is the reason for this?
Notably:
Swift-2.2.1 14.04 May 3
Should be similar for the version of 15.10. It does not seem to be the case with the master-branch tar-balls.
Its actually quite relevant for me to try to stay up to date as possible, since Swift reaks of memory leaks at this point in time.
The release of Swift 2.2 does not include the swift package manager, as the package manager was still too early in development to include in a release version of Swift at that point. Instead, a feature was added to the package manager to allow using the version from a 3.0 toolchain with the Swift from a 2.2 toolchain, so that people could use a more recent version of the package manager.
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
All Liferay docs seem to suggest that it is necessary to install the Jikes compiler in addition to the JDK. Is this really needed, to do Liferay portlet dev, or can I just suffice with the JDK.
No. As far as I know Jikes was never a strong dependency. It used to be a default compiler for older releases of Liferay. But since version 4.4 they changed to standard javac.
No. We have Liferay 5.2.3 running in a production environment. We've done a few customizations of the liferay core as well as new portlets.
I never installed the Jikes compiler, the JDK was sufficient for every task.
The last two years at least, we've been predominantly building with ecj, which is much, much faster than any JDK compiler I've ever used.
In your build.${user.name}.properties specify
javac.compiler=org.eclipse.jdt.core.JDTCompilerAdapter