Bug 190615 - [jsr269] attempting to create existing file causes an NPE
Summary: [jsr269] attempting to create existing file causes an NPE
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 186301
  Show dependency tree
 
Reported: 2007-06-01 20:26 EDT by Walter Harley CLA
Modified: 2022-06-21 07:43 EDT (History)
0 users

See Also:

Attachments
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 Walter Harley CLA 2007-06-01 20:26:20 EDT 
If a processor tries to create a file that already exists in the workspace, a compiler NPE occurs.  This should instead result in a FilerException being thrown to the processor.
Comment 1 Walter Harley CLA 2008-04-16 11:28:05 EDT 
I think overwriting "files that exist in the workspace" (or at least derived files) should be okay, because they might have been generated by APT in previous builds.  What's forbidden is overwriting files that were produced during the current build.  Both these scenarios need to be checked; the first should be supported, the second should produce a FilerException.
Comment 2 Walter Harley CLA 2010-07-20 02:31:56 EDT 
Bug 320195 addresses the second issue (attempting to overwrite a generated file in the same compile).
Comment 3 Eclipse Genie CLA 2020-06-18 11:48:17 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 4 Eclipse Genie CLA 2022-06-21 07:43:00 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.