It's intentional.
The API jar files are only intended for compiling against.
You don't need LocalStrings.properties for compiling.
You'll find more information here:
https://wikis.oracle.com/display/GlassFish/Maven+Versioning+Rules
mike_at_openbrace.com wrote on 08/21/2013 05:45 PM:
> The javaee-api-7.0.jar doesn't appear to include
> javax.servlet.LocalStrings.properties file (and its variants), even
> though the javax.servlet classes use these resources. At any rate this
> is true of the javaee-api-7.0 jars I've obtained via Maven or otherwise
> downloaded (e.g.
> http://mvnrepository.com/artifact/javax/javaee-api/7.0,
> http://download.java.net/glassfish/4.0/promoted/javaee-api-7.0-b86.jar)
>
> In contrast all of the javax.servlet-api-3.1.0.jar archives that I've
> found do include these properties files (and similarly have a
> package.html file within javax.servlet that isn't present in the
> javaee-api jar).
>
> Same is true of at least some other APIs (e.g. javax.faces) - the
> individual API's jar includes properties files etc but the javaee-api
> jar is purely the class files on their own.
>
> Is this intentional for some reason, or a mistake?
>