Im want to link an android jar library to my Xamarin project, i do everything covered by the online doc on Xamarin website.
But when i compile the binding project i got a warning that say : No Package Found.
If i replace the desired Jar by another, let say picasso.jar for example, i don't have this error and the binding projet compile without problems.
I can't link the jar library because of an NDA engagement.
But it's possible that the problems is that i get the .jar from a repository supposed to be build by maven/gradle and not a final .jar compiled?
What can i do to track the real error behind this "no package found"
A DLL is correctly generated at the end of the process, but added it to the main project don't give me any classes from the original jar.
As I thought this is the fault to the jar from maven repository. Inside the jar we got java files and not compiled files.
So i take an compiled jar (aar files) and everything work now.
Related
I have a java webapp (servlet), running in Tomcat; and a related external .jar library. Everything was fine, and suddenly, symbols (method names) can't be found. Even though I can run the app in netbeans, I can't build the app for deployment to the server: Build Failed; a series of Cannot Find Symbol errors related to an external .jar file, added as "library" in NetBeans. The library had been working fine and had not been changed:
.../src/java/com/shelterislandsoftware/alphascreen/screen/FeatureNumber.java:842:
error: cannot find symbol
this.formatType = SisFormat.valueOf(in.readUTF());
symbol: method valueOf(String)
location: class SisFormat
.../src/java/com/shelterislandsoftware/alphascreen/screen/FeatureNumber.java:911:
error: cannot find symbol
out.writeUTF(formatType.name());
symbol: method name()
location: variable formatType of type SisFormat
The source files of the SisFormat.java classes sit in the correct src folders they've always been in; the methods are present in the class and written correctly. Any suggestions? Thanks.
-- UPDATE: Now, I'm also unable to (re-)build an old JavaFx project. The java code has been built and working as an osx application; I wanted to change the icns image, and I can't rebuild. I doubt that the new image is the source of the build problem, just as I doubt that my (perfectly functional) java servlet code is the source of my build problem described above. I don't know for sure but I really suspect there's a problem with the new NetBeans 8.2 and / or osx Mojave. No one's interested, OK then. I've just copy-pasted the (formerly) library source classes directly into the main project described above, and this lets me build. It's suboptimal, as I'm using the same .jar file in a separate web app, so now I have two copies of the same classes to maintain. Oh, also, the same .jar that is unbuildable as an external jar now in this web app described above, is still perfectly buildable as an external jar in the other web app. Whatever.
I fixed this problem. The new osx (Mojave) and the newest Netbeans as of writing (8.2) are intolerant of certain package names. I fixed the problem by altering my package names. Specifically, I had projects (in their own project directory) and a library (in its own library directory). While these directories were distinct in the computer's file system, the subsegment of those paths that Netbeans considers to be the "package name" had a common root element. Both the project(s) and the library "package name" started out like com.mydomain followed by the specific name of the project or library. I fixed the problem by changing the library package name to "lib.mydomain", and all the funky build problems ceased.
I am trying to integrate my application with stardog. The application accesses already other RDF repositories in Java via sesame remoteRepository interface.
Stardog writes in http://docs.stardog.com/#_using_sesame that this can be achieved via a use of StardogRepository() - but without saying what libs to include.
After a little search inside the stardog 4.1.3 installation I found and included in eclipse's WEB-INF/lib:
stardog-api-4.1.3.jar
stardog-sesame-core-4.1.3.jar
After that, the eclipse Java compiler shows no errors in the code but one error in the project path, saying:
The project was not built since its build path is incomplete. Cannot
find the class file for
org.openrdf.repository.base.AbstractRepository. Fix the build path
then try building this project
After project cleaning this problem remains.
This class org.openrdf.repository.base.AbstractRepository is defined in the lib eclipse-rdf4j-2.0.1.jar, which is also present in the WEB-INF/lib folder (with or without this latter eclipse-rdf4j-2.0.1.jar the problem is unchanged).
What lib shell I include in order to have these 2 lines of code in http://docs.stardog.com/# compiled?
Thanks a lot in advance for any hint.
The solution is: include openrdf-sesame-4.1.2-onejar.jar and the stardog code will compile.
When I create a Scala SBT project in IntelliJ, everything works fine. I set up the jar dependencies and I can run the examples.
But if I create a Java project and try to run:
Error:(29, 28) java:
C:\workspace-java\SparkExamples\src\org\apache\spark\examples\sql\JavaSparkSQL.java:29:
package org.apache.spark.sql does not exist
I added that jar to module dependencies which contains the class in the error message. In the IDE everything seems fine, I can navigate into the JavaSparkSQL class. But when I make, it's doesn't find that class.
I added the jar to CLASSPATH, and also copy to JAVA_HOME/jdk/jre/lib/ext.
What do you think what do I wrong? What should I check?
UPDATE:
The problem is only with org.apache.spark.sql package. There are other packages what I can use. (org.apache.spark.SparkConf; org.apache.spark.api.java.JavaRDD; etc.)
UPDATE 2.:
I gave a try to Eclipse Mars, and it was completed successfully the first time. So it is an IntelliJ specific problem.
UPDATE 3.:
Something wrong with the jar file which comes with Apache Spark (spark-assembly-1.4.1-hadoop2.6.0.jar).
Eclipse has no problem with this jar.
I found that when I delete an irrelevant file from jar ("about.html") then the problem is gone. IntelliJ see every package from the modified jar.
How is this possible?
The current Jsoup release 1.7.3 has a known issue that it is using String.isEmpty() which is not supported by Android API Level 8.
I can see crash report of my app so I tried to fix this by change the source code of Jsoup and build my own jsoup.fix.jar. I test this jar with JAVA application and it worked fine on my PC.
I noticed that when I remove the original jsoup-1.7.3.jar from my project, there is errors complaining cannot find jsoup stuff, and the those errors are gone after I add the jsoup.fix.jar which seems to be good. I also check the JAVA build path and the exporting configurations, jsoup.fix.jar are all set as it should.
However, when I tried to run the APP on my Android devices, the APP crashed and saying it cannot find org.jsoup.Jsoup.
I checked the jsoup.fix.jar, opened it with JD-GUI and find the classes are all there, but I used my dex2jar to convert the classes.dex in my /bin directory, I cannot see nay org.jsoup stuff.
Just replace my jar file with the original jar will not have the same issue reproduced.
I also noticed that in my jar, the MANIFEST.MF file only have one line of content, but in the released jsoup-1.7.3.jar, the MANIFEST.MF contains a lot of content.
I am confused now, questions:
Am I doing wrong when build my own jar?
Why the APK still cannot include the jsoup pacakage even I configured it to do so?
Finally I found the reason might be the jar is exported from a JAVA project.
I have tried to create an Android project and copy the source files into it and then export another jar file, and it works!
Could anybody explain why?
I am working on DROOLS 6.0.1 application. I have my rule files (*.drl) packaged inside a separate project which is included as a jar file as a maven dependency. When I deploy my project, KIEModule is not able to find the rules files (which are packaged inside the jar above). I am not getting an error though but rules are not getting fired.
If I manually place the rules files under classpath say WEB-INF/rules/*.drl they are detected and rules are executed.
I was under impression that KIEmodules are auto discovered from anywhere in classpath.
Any pointers are appreciated. This is general question hence I have not included the comprehensive code files.
Everything start working once I place the *.drl files in the classpath (take them outside of jar).
Thanks
Step 1 : Found the solution, the package with DLR must be declared inside your : "kmodule.xml"
Step2: you have to create enter image description here
Step3:enter image description here