Posted by Xerxes Rånby on Mar 02, 2017; 3:45pm
URL: https://forum.jogamp.org/Text-without-AWT-tp4037684p4037720.html

fonts-p0.jar is only included by the artifactId named jogl
 <artifactId>jogl</artifactId>

You can check which artifactId's contain fonts-p0.jar for yourself by
looking at the maven search page here:
https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.jogamp.jogl%22

i recommend you to still use
<artifactId>jogl-all-main</artifactId>
because that is the best artifactId to use to get jogamp runtime
however if you can tell maven to also cherry pick fonts-p0.jar from the
artifactId named jogl then that would be the best and would allow the code will find the fonts at runtime.

I consider it a bug that jogl-fonts-p0.jar have been renamed fonts-p0.jar when the jogamp-scripting maven build script uploaded the jar to the maven central. Not having the correct name jogl-fonts-p0.jar  at maven central will cause a warning at runtime before jogamp locate the font as a fallback inside the fonts-p0.jar on the classpath. The warning will not stop the application from working.
However if you include fonts-p0.jar despite the incorrect jar name your application will find the fonts!