You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer I would expect the gmsecapi.jar to contain the compiled code needed to use GMSEC API and gmsecapi-javadoc.jar to contain the documentation.
Instead the gmsecapi.jar contains both the code and the documentation. This leads to several issues:
gmsecapi.jar is several times larger than it needs to be, leading to application bloat.
files in docs/ may conflict with resources used by the application.
Another instance of NASA distributing code with known CVEs (CVEs in GMSEC 4.9.1 Distribution #32) since the docs directory contains old javascript files.
The root cause seems to be not following Java development best practices of using maven build to publish the jar, javadoc jar, and source jar to maven central.
This seems to affect both the 4.x and 5.x release series.
As a developer I would expect the gmsecapi.jar to contain the compiled code needed to use GMSEC API and gmsecapi-javadoc.jar to contain the documentation.
Instead the
gmsecapi.jarcontains both the code and the documentation. This leads to several issues:gmsecapi.jaris several times larger than it needs to be, leading to application bloat.docs/may conflict with resources used by the application.The root cause seems to be not following Java development best practices of using maven build to publish the jar, javadoc jar, and source jar to maven central.
This seems to affect both the 4.x and 5.x release series.