Migrate jetty-osgi-servlet-api artifact to jetty-servlet-api

[joakime]

Along with the required build fixes from #18, we should perform the necessary steps from jetty/jetty.project#3120 to bring this artifact up to speed for JPMS as well.

Current tasks:

• Rename to jetty-servlet-api
• Implement build fixes from Update the jetty-osgi-servlet-api pom #18
• Add JPMS module-info.java that depends on jetty-schemas

[sbordet]

@joakime while we're at it, we need to add Automatic-Module-Name: jetty.servlet.api to the manifest, so Jetty 10.0.x can properly reference it.
See jetty/jetty.project#2989.

[joakime]

Example of new generated META-INF/MANIFEST.MF

Manifest-Version: 1.0
Automatic-Module-Name: jetty-servlet-api
Bnd-LastModified: 1543251475166
Build-Jdk: 9
Built-By: joakim
Bundle-Description: Combined servlet api and schemas for use in JPMS and
  OSGi environments
Bundle-DocURL: http://www.mortbay.com
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0, http://www.e
 clipse.org/org/documents/epl-v10.php
Bundle-ManifestVersion: 2
Bundle-Name: Jetty Servlet API and Schemas for JPMS and OSGi
Bundle-RequiredExecutionEnvironment: JavaSE-1.7
Bundle-SymbolicName: org.eclipse.jetty.osgi-servlet-api
Bundle-Vendor: Mort Bay Consulting
Bundle-Version: 4.0.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Implementation-Vendor: Eclipse.org - Jetty
Implementation-Version: 4.0-SNAPSHOT
Tool: Bnd-3.5.0.201709291849
url: http://www.eclipse.org/jetty

[sbordet]

Should not we require JavaSE-1.8?

[joakime]

the JavaSE-1.7 update to the OSGi environment settings for Servlet API 4.0 was done by @janbartel in commit 46bd54b
Didn't feel appropriate to adjust that.

[sbordet]

But Servlet 4.0 requires JDK 8 (Section 1.2).

[joakime]

@sbordet the SNAPSHOT for this approach is available on the jetty-snapshots repo if you want to give it a whirl.

https://oss.sonatype.org/content/repositories/jetty-snapshots/

<dependency>
  <groupId>org.eclipse.jetty.toolchain</groupId>
  <artifactId>jetty-servlet-api</artifactId>
  <version>4.0-SNAPSHOT</version>
</dependency>

This was deployed from the jetty-servlet-api-4.0-jpms branch.

[joakime]

PR #22 opened for this Issue.

[sbordet]

@joakime the Automatic-Module-Name is wrong, as module names cannot contain the - character.
Can you please use jetty.servlet.api?

[cowwoc]

I believe that jakartaee/servlet#201 is fixed. You should be able to use the artifact that was released 6 days ago, instead of the Jetty-specific fork.

[joakime]

@cowwoc unfortunately, the Jakarta specific release is missing the required embedded schemas wont work equally as well on both osgi and jpms.

[joakime]

This work has been completed