Hello ObjectBox team!
In the instructions on the README of the project, we have these instructions:
buildscript {
ext.objectboxVersion = "3.3.1"
repositories {
mavenCentral()
}
dependencies {
classpath("io.objectbox:objectbox-gradle-plugin:$objectboxVersion")
}
}
The plugin added to the classpath is in MavenCentral, this is the latest published version.
As an educated developer, I downloaded the sources jar, so that I could validate the source code that my app is using.
Inside that file, however, there's only a README file:
Not available yet
And naturally, by downloading the Jar file, only .class files are available.
For this reason, the gradle plugin is considered proprietary code. And this has lead F-Droid - the main FLOSS Android distributor - has blocked many apps, such as
And probably more to come.
This is a very serious bug.
I imagine it's somewhere where the code is published to MavenCentral that is not including the source codes.
This issue is a blocker for anyone that wants to integrate ObjectBox to an 100% FLOSS app, such as ones deployed to F-Droid
Hello ObjectBox team!
In the instructions on the README of the project, we have these instructions:
The plugin added to the classpath is in MavenCentral, this is the latest published version.
As an educated developer, I downloaded the sources jar, so that I could validate the source code that my app is using.
Inside that file, however, there's only a README file:
And naturally, by downloading the Jar file, only
.classfiles are available.For this reason, the gradle plugin is considered proprietary code. And this has lead F-Droid - the main FLOSS Android distributor - has blocked many apps, such as
And probably more to come.
This is a very serious bug.
I imagine it's somewhere where the code is published to MavenCentral that is not including the source codes.
This issue is a blocker for anyone that wants to integrate ObjectBox to an 100% FLOSS app, such as ones deployed to F-Droid