Plugin [id: 'io.jmix', version: '1.2.0'] was not found

Support
#1

I just created project Jmix version 1.2.4 and now getting the following error:

org.gradle.api.plugins.UnknownPluginException: Plugin [id: 'io.jmix', version: '1.2.0'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'io.jmix:io.jmix.gradle.plugin:1.2.0')
  Searched in the following repositories:
    Gradle Central Plugin Repository

Thank you in advance

#2

Artefacts of all released versions of Jmix are available in the repositories.
Perhaps it’s a network issue on your side.

#3

Hi,
I just ran into the same issue.

I am behind corporate proxy so I haven’t direct access to public Maven repositories where the jmix gradle plugin stored.

My solution:
I added the https://nexus.jmix.io/repository/public/ repository to the corporate nexus as a proxy repo then added this proxy to my normal group repository.

I started the new project with my normal repository so jmix put it into build.gradle.

As next step after got the error I added the folowing lines to the settings.gradle:

pluginManagement {
    repositories {
        maven {
            url 'https://link.to.your.artifactory.repo'
        }
    }
}

After that the ‘gradle build’ will run successfully.

Alternatively you can put it into USER_HOME/.gradle/init.gradle this way:

settingsEvaluated { settings ->
    settings.pluginManagement {
        repositories.clear()
        repositories {
            maven {
                url 'https://link.to.your.artifactory.repo'
            }
        }
    }
}

This way still need to rerun ‘build gradle’ but you can keep settings.gradle untouched in the project.

Best Regards,
Zoli

* Exception is:
org.gradle.api.plugins.UnknownPluginException: Plugin [id: 'io.jmix', version: '1.4.2'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'io.jmix:io.jmix.gradle.plugin:1.4.2')```
1 Like
#4

Let me note that Jmix repositories do not contain released versions of Jmix Gradle plugin. So your corporate repository should also mirror the Gradle Plugins repo, see Gradle - Mirroring the Plugin Portal

Also, instead of nexus.jmix.io better use global.repo.jmix.io for reliable worldwide access.

#5

I also get this error and have no idea, how to solve that issue:
tried global.repo and also nexus…
both repositories I can browse via Edge browser…
I use the Temruion 11 SDK version
there is no proxy used for the internet connections

Build file ‘D:\Daten\Cuba\examples\build.gradle’ line: 2

Plugin [id: ‘io.jmix’, version: ‘1.5.0’] was not found in any of the following sources:

  • Try:

Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

  • Exception is:
    org.gradle.api.plugins.UnknownPluginException: Plugin [id: ‘io.jmix’, version: ‘1.5.0’] was not found in any of the following sources:
  • Gradle Core Plugins (plugin is not in ‘org.gradle’ namespace)
  • Plugin Repositories (could not resolve plugin artifact ‘io.jmix:io.jmix.gradle.plugin:1.5.0’)
    Searched in the following repositories:
    Gradle Central Plugin Repository
#6

I have the same problem.

Screenshot 2023-03-29 at 11.16.44

the problem appeared after i updated Intellij to new version.

Screenshot 2023-03-29 at 11.24.35

#7

Hi, we are using Idea 2022.3.x…
We tested it on another server, there it works.
Actually we are working with the network team to find out,
which settings in the VPN client is causing the issue…

#8

As I see Gradle is experiencing some issues with plugin portal, see https://status.gradle.com/

Maybe this was the reason of your problem.

#9

nope, it has nothing to do with that plugin portal issue… that one got solved meanwhile, but our issue still exists

1 Like
#10

I downgraded the Intellij version, then the problem was solved

#11

Hi,
took some time, but now we found the root cause:
the new used VPN client is blocking the repo URLs in the Internet Security part of the client.
We need to whitelist them …
Thx
Roland