Bug 429371 - j2ee maven
Summary: j2ee maven
Status: RESOLVED WORKSFORME
Alias: None
Product: EPP
Classification: Technology
Component: jee-package (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2014-03-01 00:54 EST by eclipseyf wo CLA
Modified: 2021-05-31 10:32 EDT (History)
3 users (show)

See Also:


Attachments
error pic (37.45 KB, image/png)
2014-03-01 00:54 EST, eclipseyf wo CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description eclipseyf wo CLA 2014-03-01 00:54:47 EST
Created attachment 240422 [details]
error  pic

create  maven   has  error
Comment 1 David Williams CLA 2014-03-01 01:20:12 EST
This looks like the Java EE package in EPP.
Comment 2 eclipseyf wo CLA 2014-03-01 22:21:39 EST
这个问题是:
我用 kepler sr2 的 j2ee版本 创建 maven 的web项目的时候 报的错误

就如之前图片中所提示的信息
Comment 3 eclipseyf wo CLA 2014-03-02 01:12:50 EST
kepler sr2 的 j2ee版本 
创建web型工程  maven web  或是 dynamic web 
只要 有 jsp
报错:
The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path	*.jsp
Comment 4 eclipseyf wo CLA 2014-03-04 22:34:49 EST
我英语 不行  所以 写不了
因此 我用中文 描述的

希望咱们 eclipse 团队 能够 给出 出现这个问题的 具体 问题 期望 修复下 这个问题
Comment 5 eclipseyf wo CLA 2014-03-08 02:02:24 EST
The problem is not solved?

As long as the project in the new JSP, reported error:

The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path	*.jsp
Comment 6 Nitin Dahyabhai CLA 2014-06-25 12:14:19 EDT
(In reply to eclipseyf wo from comment #5)
> The problem is not solved?
...
> The superclass "javax.servlet.http.HttpServlet" was not found on the Java
> Build Path	*.jsp

Does a Clean and Build of the project keep showing the error? *Is* that class on the Java Build Path of the project?
Comment 7 Nitin Dahyabhai CLA 2021-05-31 10:32:06 EDT
No further information, among other things, showing that the class was actually on the Build Path.