> Could not resolve all files for configuration ':classpath' - java

I'm trying to rebuild a project in order to be compatible with Google Play store requirements, however the code was generated on earlier version of android 8, I got the code & trying to rebuild faced many issues & covered most of them, however last issue I"m facing now is receiving the following when I Sync, any idea to stope this error in order to build the project?
Sync error:
problem occurred configuring root project 'ascc-android 2'.
Could not resolve all files for configuration ':classpath'.
Could not find io.realm:realm-gradle-plugin:6.0.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.pom
- https://repo.maven.apache.org/maven2/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.pom
Required by:
project :
Possible solution:
Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

Related

Error when trying to integrate JavaFX with Hibernate

I'm trying to integrate javaFX with Hibernate using Maven on Intellij. When I first created a Hibernate project, and added some JavaFX dependencies to it. I ran and
Error: JavaFX runtime components are missing, and are required to run this application
Then I decided to add "module-info.java" file to the project, this happened as described below . I already tried to trace to the end of this error on the right this time, tried every possible solutions... and finally it was just a dead end for me. So I has been wondering if I did anything wrong?
Error happened after module-info.java added:
Caused by: java.lang.NoClassDefFoundError: net/bytebuddy/NamingStrategy$SuffixingRandom$BaseNameResolver
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.cfg.Environment.buildBytecodeProvider(Environment.java:345)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.cfg.Environment.buildBytecodeProvider(Environment.java:337)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.cfg.Environment.<clinit>(Environment.java:230)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.boot.registry.StandardServiceRegistryBuilder.<init>(StandardServiceRegistryBuilder.java:141)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.boot.registry.StandardServiceRegistryBuilder.<init>(StandardServiceRegistryBuilder.java:96)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.cfg.Configuration.reset(Configuration.java:158)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.cfg.Configuration.<init>(Configuration.java:124)
at org.hibernate.orm.core#5.4.18.Final/org.hibernate.cfg.Configuration.<init>(Configuration.java:118)
at myModule/controller.LoginController.login(LoginController.java:44)
... 58 more
Edited: I'm exploring, reading some projects on Github and find it may relevant to module in Java 9? I see they separate their code into modules and in each module it like... independent maven projects with its own pom.xml file, one has only javafx dependency; another has only hibernate dependency.
Here is the project I'm reading

Error in Creating a Maven project in Eclipse IDE

I just started to learn Hibernate in Java and i was supposed to use Maven Project but while creating project i am facing this error why i am getting this error almost tried all of the online saying still no improvement it fails ...Thanks in Advance
Could not resolve archetype org.apache.maven.archetypes:maven-archetype-quickstart:RELEASE from any of the configured repositories.
Could not resolve artifact org.apache.maven.archetypes:maven-archetype-quickstart:pom:RELEASE
Failed to resolve version for org.apache.maven.archetypes:maven-archetype-quickstart:pom:RELEASE: Could not find metadata org.apache.maven.archetypes:maven-archetype-quickstart/maven-metadata.xml in local (C:\Users\Manoj Selvin.m2\repository)
Failed to resolve version for org.apache.maven.archetypes:maven-archetype-quickstart:pom:RELEASE: Could not find metadata org.apache.maven.archetypes:maven-archetype-quickstart/maven-metadata.xml in local (C:\Users\Manoj Selvin.m2\repository)

Gradle project sync fails

I get this error:
Gradle project sync failed
I don't understand how to use the levels that the other users said and unfortunately didn't get my problem solved. I'm a beginner.

Maven Build Error - Firefly Plugin - No plugin found

I have tried several methods to resolve this issue.
I am trying to install the Vaadin Starter App "Bakery"
Version using : Java, Shiro, Vaadin Platforms.
Error on build failure:
No plugin found for prefix 'firefly' in the current project and in the plugin groups
I've tried methods listed [here][1]
and another post by deleting my .m2/resources and letting it repopulate. and also a mvn clean install, but I keep getting same error messages.
Here is a [link][1] to the error messages:
Above the plugin error are some type of fetch cant get meta data messages.
I'm thinking it needs a different version of a plugin, needs pom file or settings file edited, but just have not found solution yet.
No plugin found for prefix 'firefly' in the current project and in the plugin groups
I believe it was with the plugin causing a problem. I went to this link, found the file, over-wrote the existing file with the one at the link, did a rebuild and it worked.
Maven-compiler-plugin

How to resolve missing artifact error when using Eclipse AWS plugin?

I am using the aws Java plugin for Eclipse. I didn't have any issues during the installation process but after I used the plugin to create a sample DynamoDB project, I got this error
Missing artifact com.amazonaws:aws-java-sdk-cl....watchmetris.jar:1.11.123(click for 156 more...).
clicking didn't do anything.
I thought the error was due to the fact that I didn't install that jar during the installation process - I only installed "AWS Toolkit for Eclipse".
I went back into Eclipse and installed every non optional plugin from the aws(see below)
After I restarted Eclipse and tried creating my DynamoDB project again, I get a different failed to read artifact descriptor error(see below)
Has anyone experienced this issue before or know what the solution is? Elastic load balancer should be apart of AWS Toolkit which I installed. I've tried removing and reinstalling the aws plugin but I'am still getting missing artifact errors. I've looked at other threads on AWS plugin for Eclipse as well.
For anyone dealing with this issue with this issue, I got it to work! I can't really explain why it works though - maybe Maven's way of resetting some setting.
What I did was go inside pom.xml, the configuration file for Maven, and into the Dependencies tab. This is what I saw
I reasoned that the missing artifact was in the aws-java-sdk jar so I removed it. I then deleted the project from disk and created a new one. The new project came with the correct dependencies and no compiler errors!
The problem is not your AWS Toolkit, it's a problem of your Maven. Please try to create a project with Maven to check if Maven's setting is correct. If Maven is correct, please see your pom file in XML and check the dependency is correct? If you cannot create Maven project, it's means that your Maven setting is wrong somewhere!
I received a similar error "failure to transfer com.amazonaws:aws-java-sdk ...". The pom resolution could work, but here's another solution. So, when you start an aws project for the first time, certain artifacts necessary for maven are stored under .m2\repository\com\amazonaws.
What happened to me was that when I deleted one of my aws projects, I also deleted the resources being referred to which was somewhere in the aforementioned directory. And because the directory existed, eclipse's aws toolkit didn't bother downloading it again. I solved it by just deleting the $home.m2\repository\com\amazonaws directory. So next time I created a new aws project, it had to download all the artifacts.

Categories

Resources