Need more explanation about "import javax.ws.rs.*" there are more then one choice. about jakartaee-firstcup HOT 6 OPEN

• Issue Imported From: javaee/firstcup#10
• Original Issue Raised By:@deglans
• Original Issue Assigned To: Unassigned

from jakartaee-firstcup.

@deglans Commented
After many research it's same to be javaee-api the most correct answer...

from jakartaee-firstcup.

@deglans Commented
Sorry, i have accidentally close the issue...

from jakartaee-firstcup.

@bshannon Commented
If you're building a Java EE application for deployment to a Java EE application server,
then compiling against the javaee-api jar file is the right thing to do. Be sure to list it as
a "provided" dependency since you don't want that jar file included in your application
at runtime.

from jakartaee-firstcup.

@deglans Commented
Do you mean this (https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html):

provided
This is much like compile, but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided because the web container provides those classes. This scope is only available on the compilation and test classpath, and is not transitive.

So the pom.xml become:

<dependency>
   <groupId>javax</groupId>
   <artifactId>javaee-api</artifactId>
   <version>8.0</version>
   <type>jar</type>
   <scope>provided</scope>
</dependency>

Is that right?
I think this explanation should be included in the tutorial....

from jakartaee-firstcup.

@bshannon Commented
Yes.

from jakartaee-firstcup.