gradle7.4.2 can not implementation local jar
the error is npe.
* Exception is:
org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':client:rest'.
at org.jetbrains.plugins.gradle.model.ProjectImportAction.execute(ProjectImportAction.java:116)
Caused by: java.lang.NullPointerException
I need to use local jar into project, used gradle 5.4.2 is success, but use 7.4.2, always error...
I use many method to test, but can not access...
enter image description here
how to handle the exception?
thanks~~~
Related
I'm trying to assemble an Android app in Bamboo server, but I'm getting this error when the assemble comand run. Note: It works perfectly in local.
Command running:
gradlew assembleDebug
And the error I get:
Caused by: org.gradle.internal.UncheckedException: java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource compilation failed
C:\Windows\System32\config\systemprofile\.gradle\caches\transforms-2\files-2.1\aa6199e981580f79dc21c6ea06a3575f\res\drawable-mdpi-v4\quantum_ic_skip_next_white_24.png: error: file not found.
I've checked for the resource and its use, but it's not from my project code. It belongs to an external library: play-services-cast-framework
I've been also checking other similar post, but the error can be caused for many resources reasons, so I've not found a solution.
Some solutions suggest that is a problem at some gradle plugin version, but I'm already using version 3.3.1
Any help or clue?
Thanks!
Updated:
It's been days that I tried to accomodate some times in between then came back to this code-base, but still faced up the same issue.
I am frustrated that have a Spring Boot 1.5.12 application that worked in IDEA but failed when running executable jar in Unix box, and the stack trace follows this format that I needed to trim the stack trace for relevancy:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xxxEntityManager' defined in class path resource [com.abc.persistence.ConfigClass]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: Unable to resolve persistence unit root URL
................. [Skipped the stack strace]
Caused by: java.io.FileNotFoundException: class path resource [] cannot be resolved to URL because it does not exist
at org.springframework.core.io.ClassPathResource.getURL(ClassPathResource.java:187)
at org.springframework.orm.jpa.persistenceunit.DefaultPersistenceUnitManager.determineDefaultPersistenceUnitRootUrl(DefaultPersistenceUnitManager.java:602)
... 48 common frames omitted
As per suggestion by Getting "Unable to resolve persistence unit" error when building jar without IDE, I tried this workaround of 2 changes but it doesn't work at all.
1)#EnableAutoConfiguration(exclude = HibernateJpaAutoConfiguration.class) to my application class
2)spring.data.jpa.repositories.enabled=false to my application.yml file in src/main/resource/ directory
Even with those two changes being added, it still shows the same error.
I hope someone can help me figure out this frustrating inconsistency occured between the run time behavior in IDEA and executable jar in console.
Edit:
I used Gradle build script with this build task applications to build the app jar executable whose jar pull everything of src files in package names and resource property configuration yaml files besides gradle build:
applications {
...
}
So I've been tried to crack the root cause that runs my life nuts, which is based on this possible mystery:
Can someone know about jar (JVM) process of how it processes to create jar artifacts that in the end when I face the extremely weird anomaly where Intellj has always been able to set the persistence unit URL to default, whereas running on jar doesn't accomodate this auto-configuration already coded in the app and property codes?
When we try to use ejbdeploy.sh to for ejb jars getting below exception in IBM WAS 8.5 version.
$TEST.jar Error executing deployment: org.eclipse.core.runtime.CoreException. Error is Plug-in com.ibm.etools.ejbdeploy was unable to load class com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension..
$TEST.jar org.eclipse.core.runtime.CoreException: Plug-in com.ibm.etools.ejbdeploy was unable to load class com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.
$TEST.jar at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
$TEST.jar at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
Note: every time it is failing with different jars.
People,
With new SonarQube version for C# plugin -Dsonar.branch=X parameter is throwing error. The error is as follows:-
Sonar failed with error: 'ERROR: Error during Sonar runner executionERROR: Unable to execute SonarERROR: Caused by: Fail to decorate 'org.sonar.api.resources.File#56b0f44f[key=Aspects/MethodPerformanceAttribute.cs,deprecatedKey=Aspects/MethodPerformanceAttribute.cs,path=Aspects/MethodPerformanceAttribute.cs,dir=Aspects,filename=MethodPerformanceAttribute.cs,language=C#]'ERROR: Caused by: Resource org.sonar.api.resources.File#56b0f44f[key=Aspects/MethodPerformanceAttribute.cs,deprecatedKey=Aspects/MethodPerformanceAttribute.cs,path=Aspects/MethodPerformanceAttribute.cs,dir=Aspects,filename=MethodPerformanceAttribute.cs,language=C#] was not found in InputPath cacheERROR
This error goes away and sonar run is succeessful if i remove the -Dsonar.branch parameter. Can someone provide more information on this.
This issue has been solved in SonarQube 5.1, see http://jira.codehaus.org/browse/SONAR-6250 for additional details.
mvn install sakai:deploy is running successfully but at run time it gives error
org.sakaiproject.portal.api.PortalHandlerException:
java.lang.IllegalArgumentException: Unable to find registered context
for tool with ID sakai.employee
at org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:862)
caused by: java.lang.IllegalArgumentException: Unable to find
registered context for tool with ID sakai.employee
at ... (check the revision history for full stacktrace)
Check catalina.out for errors when you start Tomcat.
The tool web app has not started up.
You'll need to resolve those errors before the tool will load.