ClassLoader | PHP 5.3 class-based autoloader using namespaces | Build Tool library

I'm having exactly that issue with my M1 Mac Mini.

You need to add scala-compiler configuration to your pom.xml. The problem is without that there is nothing to compile your SparkTrans.scala file into java classes.

Add:

You can simply create the class file MainActivity.java with the Java code.

The log shows that the ResourcesPlugin is being found but its plug-in activator is getting a null pointer exception when it tries to get the IContentTypeManager.

The content type manager is provided using OSGi declarative services but you have not included org.apache.felix.scr which deals with this.

So at a minimum you need to include org.apache.felix.scr and start it in the section:

I believe if you make use of either of the two as below will solve your issue.

1. InputStream in = FileInputStream(PathOfYourFile)
2. API's available in Paths class available in java.nio.file package.

Issues

You have a UNIQUE index on the NUM_JUG column (perhaps implicit if NON_JUG is defined with PRIMARY KEY) and you are using the standard update method which uses the default conflict action of ABORT and therefore fails if an attempt is made to duplicate a NOM_JUG value.

As secondary issue is that the SQLiteDatabase update method returns the number of updates (see extract and link below) (same for updateWithOnConflict). The number returned will never be -1 it will be 0 or more (0 indicating that no updates have been applied).

As per SQLite Database - Update

Returns

int the number of rows affected

Fix

To fix the main issue you should use the updateWithOnConflict method. This takes a 4th parameter a conflict and you probably want IGNORE so you could use :-

At the end of your log, just before the initial crash. there is a warning:

Default FirebaseApp failed to initialize because no default options were found. This usually means that com.google.gms:google-services was not applied to your gradle project.

simply adding com.google.gms:google-services should fix any issues you have, if you have issues, ensure your Gradle cache is cleared or run without the build cache --no-build-cache

This cited article is wrong, even with these undefined terms like “preload” and “when the program first actively uses the class”.

If “preload” is supposed to mean eagerly resolving referenced classes, we can refer to the Java Language Specification, §12.1.2.:

An implementation may resolve symbolic references from a class or interface that is being linked very early, even to the point of resolving all symbolic references from the classes and interfaces that are further referenced, recursively. (This resolution may result in errors from these further loading and linking steps.)

It then states about the potential errors:

The only requirement on when resolution is performed is that any errors detected during resolution must be thrown at a point in the program where some action is taken by the program that might, directly or indirectly, require linkage to the class or interface involved in the error. Using the "static" example implementation choice described above, loading and linkage errors could occur before the program is executed if they involved a class or interface mentioned in the class Test or any of the further, recursively referenced, classes and interfaces.

So it’s definitely wrong to say that loading or linkage errors were only reportable “when the program first actively uses the class”, even when the article didn’t care to explain what constitutes an active use.

As explained in this answer, initialization is performed under well defined conditions and the behavior of your program is understandable when overcoming the common confusion of loading and initialization. To evaluate the expression MyChild1.str, loading of the class MyChild1 is unavoidable and only after the class has been loaded, it is possible to determine that it doesn’t have a field str but a superclass that has. So while it will be unavoidably loaded it will not get initialized, as neither of the specified actions (like the access to a static field) has been performed.

As you can recognize from your stack trace, the NoClassDefFoundError has been thrown right before evaluating the expression MyChild1.str, which is already as lazy as possible. Valid places to throw the error would have been the beginning of the method’s execution, the loading and resolving of the Mytest1 class, or, as the linked part of the specification says, even before the execution of the entire program starts.

While the point of loading and resolving and hence, the point of throwing the error, is left to the particular implementation, all valid implementations will agree in throwing the error before coming to evaluate the expression MyChild1.str.

First thought: Probably mixed up index number with number of elements?

But to be certain I have to see the actual code where the exception is thrown.

Not meant to be disrespectful: https://docs.oracle.com/javase/tutorial/java/nutsandbolts/arrays.html