How do you install griffon version 2.5? If I run
sdk list griffon
it shows me version 1.5 as latest version.
Griffon 2.x is not available as an sdk candidate because it no longer has a command line of its own. You either use gradle or maven to build Griffon 2.x projects. You have the option to initialize a project using lazybones however that's not a hard requirement, you can create the project from scratch if you like.
Be warned that IntelliJ has a Griffon plugin. This plugin does not work with Griffon 2.x (http://griffon-framework.org/tutorials/1_getting_started.html#_tutorial_1_4) and its usage is discouraged.
AFAIK there's no lazybones support in IntelliJ for project creation.
Related
With Android Studio 3.3 I use native (C++) library, which I built with CMake. The Android plugin (v. 3.2.1) will choose the 'builtin' or 'external' cmake, depending on the configuration of externalNativeBuild, as documented at developer.android.com.
I want to add an extra custom task (install) that should use the same cmake version as the Android Plugin. But even with the 'builtin' cmake, it's not clear what the path is. I can find android.sdkDirectory, but even there I have today sdk\cmake\3.6.4111459 and sdk\cmake\3.10.2.4988404, and for some strange reason, some of my projects choose 3.6, while others use 3.10. This contradicts the official the release notes for Android Studio that "Gradle still uses version 3.6.0 by default", but well…
How can I decide which to use, without reimplementing the Android Plugin's obscure logic?
One workaround that may help, parse the first line of the generated file .externalNativeBuild/cmake/debug/armeabi-v7a/cmake_build_command.txt:
Executable : C:\local\Android\sdk\cmake\3.10.2.4988404\bin\cmake.exe
This still needs some adjustments, because the later versions of build tools will use .cxx instead of .externalNativeBuild; the build variant names may be different too.
Android Studio will pick up the latest CMake version under sdk\cmake, but you can configure your particular version from
externalNativeBuild {
cmake {
...
version "cmake-version"
}
}
And specify our custom CMake director as below inside local.properties
cmake.dir="path-to-cmake"
Or, you can choose NOT to upgrade your CMake from SDK Manager (just to delete the sdk\cmake\<version to delete> folder will be fine) so that you can stick to the CMake version your project is comfortable with.
I have downloaded a previous version of Android Studio (3.0.1) since I must use the android gradle plugin version 3.0.1 and gradle 4.1.
The code, and the other modules it depends on, were written using Android Studio 3.2, kotlin 1.3.10 and gradle version 4.10.2
When I try to synchronize the project with the older version of Android Studio (3.0.1) or running gradlew assembleDebug it says the minimum gradle version is 4.6 even though the gradle wrapper version is 4.1 and the gradle plugin version is 3.0.1. The kotlin version for all dependencies was set on 1.2.41
This is the error:
Minimum supported Gradle version is 4.6. Current version is 4.1.
Please fix the project's Gradle settings. Fix Gradle wrapper and
re-import project Gradle settings
How can I compile such project using older the older version?
You have to use newer gradle wrapper and plugin in order to compile your project, if you want to use AS 3.2. So there is two options for you - upgrade wrapper and plugin, or downgrade AS, plugin, wrapper and kotlin in all dependencies.
I have followed the instructions in https://github.com/mbats/eclipse-buildroot-bundle/wiki/Tutorial-:-How-to-activate-and-install-the-Buildroot-Eclipse-plugin-%3F for installing the plugin.
Buildroot's server for eclipse plugins (https://buildroot.org/downloads/eclipse/) does'nt contain plugin for eclipse MARS version (v4.5).
I tried to install the 'Luna' version (v4.4) plugin but I got my toolchain list corrupted.
I tried starting-up eclipse with the -clean flag in the 'eclipse.ini' file but it didnt help either.
How can I make eclipse "register" buildroot plugin for eclipse versions higher than 4.4 ?
The plugin supports at most Eclipse Luna at the moment. Work is on-going to support higher versions.
I've recently get update notification of android studio 2.3, after the update it's not opening any project and throwing error:
[plugin: com.darkklord.gradle.metric.core]
after downgrading and reinstalling i still have this issue, can anyone please help me on this topic ?
Download latest plugin from here: https://plugins.jetbrains.com/plugin/9197-android-gradle-metrics--checkstyle
Install Plugin manually from disk.
Restart Android Studio (The error will still occur)
Remove plugin in IDE.
Restart
You might also uninstall the refrenzed plugins Checkstyle and PMD
You need to change your dependency
classpath 'com.android.tools.build:gradle:3.1.0'
Sometimes you need to change name of project manually(look at AndroidStudioProjects folder) that you opened lastly.
After changing name, android studio will show all projects,
open one of them,
in file menu,
click open button,
then open your desire project (or change its name to its previous name)
change build:gradle plugin to:
classpath 'com.android.tools.build:gradle:3.3.2'
(in app gradle file)
I made sure that my Gradle version was compatible with my android gradle plug in. In my case I was using Gradle 6.0.1 and when I changed my android gradle plug in to version 3.5.3 the problem went away.
Project Structure----->> Project ------>> Android Gradle plug in version 3.5.3.
[https://docs.gradle.org/6.0.1/release-notes.html
[Java 14 and later versions are not yet supported.
Compatibility Notes
A Java version between 8 and 13 is required to execute Gradle.
Java 6 and 7 can still be used for compilation and forked test execution. Just like Gradle 5.x, any supported version of Java can be used for compile or test.
This version of Gradle is tested with
-------->>>>>>>>Android Gradle Plugin 3.4, 3.5 and 3.6
Kotlin 1.3.21 through 1.3.50
Other versions may or may not work.]]]]
I hope this helps
I updated Xamarin Mvvmcross 3.2.2 project to 3.5 for Unified API support.
Mvvmcross.HotTuna 3.5 package is added in project.
So there are Mvvmcross.HotTuna.CrossCore and Mvvmcross.HotTuna.MvvmCrossLibraries packages can be seen under Package folder.
But cannot find binding assemble, so "using Cirrious.MvvmCross.Binding;" is not resolved.
And MvxTouchSetup is also not resolved
The project worked well with Mvvmcross3.2.2.
Now what other nuget packages should be added in the project?
No package is added newly.
The 3.5 libraries package has been updated to include the new MvvmCross.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.MvvmCrossLibraries.3.0.1.nuspec#L72
The 3.5 crosscore package has bee update to include the new MvvmCross.Binding.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.CrossCore.3.0.1.nuspec#L91
If the update isn't working for you:
read the advice on http://kerry.lothrop.de/unified-api-for-xamarin-ios/ about how to update the unified
check you have updated your own project to Xamarin iOS unified
check you have up-to-date nuget installed
clean, rebuild, swear and retry until it all works