Bug 537503 - Eclipse can't compile class in java ee project，
Summary: Eclipse can't compile class in java ee project，
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.9   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-30 10:22 EDT by zhang j CLA
Modified: 2023-02-10 18:29 EST (History)
0 users

See Also:

Attachments
This is the eclipse ".setting" environment (2.70 KB, application/x-bzip)
2018-07-30 10:22 EDT, zhang j CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description zhang j CLA 2018-07-30 10:22:17 EDT 
Created attachment 275194 [details]
This is the eclipse  ".setting"  environment

Eclipse can't compile any class, but the jar package introduced by gradle can be generated normally. 


I used the Gradle command to compile war, but it was very successful, no error, using eclipse ui to deploy tomcat does not always compile class   

```shell 

```

If you can, I hope to agree on a point in time, remotely my computer reproduces this bug.
Comment 1 Eclipse Genie CLA 2020-07-20 08:57:37 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-02-10 18:29:00 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.