I'm upgrading from 6.1 GA1 to 6.1 GA3, but have problems with Kaleo-Web 6.1 GA1. Could it be that it's not compatible with 6.1 GA3?
You should be able to connect to marketplace and download the latest kaleo-web version. Most likely the GA1 version of the plugin is not compatible with Liferay GA3 - at least it has naturally not been tested. But plugins are typically released together (or shortly after) a new portal GA has been released.
Please download the latest version from the Marketplace and check its compatibility. By the way, this applies to all plugins that you have deployed, not just kaleo-web
Related
I'm migrating from VS2015 to VS2017, and updating a repo's solutions to be able to be compatible with VS2017. In the process, I'm also updating the Azure SDK version from 2.7 to 3.0.
I'm setting up a fresh dev environment, and installed Azure SDK 3.0 via VS2017's Azure development workload.
When I opened the solution file in the repo, I got one notice per cloud service project that its Microsoft Azure Tools version was getting upgraded from 2.7 to 2.9...
...and the ProductVersion tag in the corresponding .csproj files was updated from 2.7 to 2.9.
Questions:
Why wasn't this updated to 3.0?
Is there anyway for me to update it
to 3.0 without manually editing the csproj file? I don't see an
option to do so in Properties when I right click the cloud service
projects in Solution Explorer.
Is there some reason I shouldn't be
doing this?
"Microsoft Azure Tools - v2.9" mentioned in your screenshot is just a little misleading.
Underlying reason is that Microsoft hasn't really changed the version number of most components as part of 3.0 SDK release. Even the binaries get installed in the same folder as 2.9.
Good news is that you don't need to do anything special apart from converting the project to target latest version, which you're already getting prompted for.
So once you do convert your project as per the prompt, you're essentially working with SDK 3.0, even though version string says v2.9, because as the links explain, most of the components haven't changed major version number as part of SDK 3.0 version (when comparing with 2.9)
Here are some of the links which talk about this -
Azure SDK for .NET 3.0 Release Summary
No breaking changes to the Azure SDK 3.0 have been introduced in this
release. There is also no upgrade process needed to leverage this SDK
with existing Cloud Service projects. To allow use of the Azure SDK
3.0 without requiring an upgrade process, Azure SDK 3.0 installs to the same directories as Azure SDK 2.9. Most the components did not
change the major version from 2.9 but instead just updated the build
number.
Visual Studio 2017 latest installer does not install Azure SDK 3.0
In this link look at the response from Devin Breshears - MSFT
Azure 3.0 SDK Install Weirdness
An independent blog talking about the same issue.
I started to read about wicket integration with liferay. I found very old information that wicket portlet is no longer supported, but wicket version 1.5.6 works fine with liferay 6.0. What about Liferay 6.2?
Just yesterday a user from the community created a Pull Request to fix the support for Liferay: https://github.com/wicketstuff/core/pull/476.
The Pull Request is for WicketStuff 7.x though. You are very welcome to port the fixes to wicket-6.x branch and we will add them for WicketStuff 6.23.0.
WicketStuff 1.5.x is not maintained anymore.
Apache Wicket version 6.x, 7.x and 8.x supports JSR286 portlets.
Please see the following wiki of how to use the apache wicket portlet bridge.
https://github.com/wicketstuff/core/wiki/Portlet
I am planning to install my j2EE, spring rest based application on Red Hat Enterprise Linux 6.1. I want to know about the software version which is compatible. I am not sure whether all the new versions are compatible in REL 6.1.
The list of software's I need to install are
J2EE
Apache Tomcat
SpringRest
MySQL
The RHEL 6.1 can easily be updated for the latest versions of Java, Tomcat. For the latest MySQL, if there are dependencies not present in RHEL 6.1 then you could try either adding or updating them (using yum or building from source).
J2EE: Download from Oracle Java SDK download page [I believe you want JDK since the J2EE dependencies would be provided by Tomcat such as Servlet etc]
Apache Tomcat: Download the binaries from the tomcat apache website [http://tomcat.apache.org/]. That should be enough to get you started. If later on you would like to use openssl or apache portable runtime then that is easily setup as well. The tomcat documentation has useful documentation to set it up.
SpringRest: I believe you are referring to the java archives for it. You can use Maven to download the necessary dependencies or use Spring Boot (https://spring.io/guides/gs/rest-service/) or search Google for the many examples of bundling Spring dependencies with your application.
For MySQL: refer to http://dev.mysql.com/doc/mysql-repo-excerpt/5.6/en/linux-installation-yum-repo.html
How do I fix:
warning MT1108: Could not find developer tools for this 6.1.3 (10B329) device. Please ensure you are using a compatible Xcode version and then connect this device to Xcode to install the development support files.
I updated my iPad to new version of iOS and this started happening...I updated my xcode version to the latest stable version (Xcode 5, I believe)...I still have `xcode 4 on my computer how do I get this stop happening...
You'll need Xcode 4.6 - which was the version shipping support for the iOS 6.1 SDK. Xcode 4.5 shipped support for iOS6 while Xcode 5 previews (not stable) ships support for iOS7.
In general a later version will be ok, but sometimes the changes are too big (e.g. moving from gcc to clang) that this might not work. Also the NDA around iOS7 and Xcode5 means you're unlikely to get help here (or in other public forums).
So if you're developing for iOS 6.1 (the released, stable version of iOS) you should be using Xcode 4.6 (the stable tools/SDK) so you can deploy your applications to the appstore.
I have a portlet that worked fine on Liferay 6.1 portal but when I deploy it on Liferay 5.2.3
my configuration page did not even open.
How should I make it work ?
Here is a nice authoritative answer to a very similar question.
The portlets of newer versions are not designed to work on older installation of Liferay. Since they are compiled using the latest plugins-sdk and the also the different jars which have changed since the last version.
So if you want the newer version portlet to work with any older version then you have to compile the portlet with an older version of Liferay with that plugins-SDK. And I am sure there would be a lot of classes and jsp-tags in the Liferay 6.1 portlet which would not work in Liferay 5.2.3.