Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 498988 - [releng] Dirty git status after build in eclipse.jdt.debug
Summary: [releng] Dirty git status after build in eclipse.jdt.debug
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.6   Edit
Hardware: PC Linux
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 420078
  Show dependency tree
 
Reported: 2016-08-01 09:10 EDT by Andrey Loskutov CLA
Modified: 2020-04-16 03:19 EDT (History)
1 user (show)

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 Andrey Loskutov CLA 2016-08-01 09:10:20 EDT 
I'm trying to build JDT as part of the SDK build and I see that after the (failed) build "git status" reports:

cd eclipse.jdt.debug
git status
Untracked files:
  (use "git add <file>..." to include in what will be committed)

        org.eclipse.jdt.debug/jdi.jar
        org.eclipse.jdt.debug/jdimodel.jar

Ideally this should not happen, build should not create "untracked" files - they either should be deleted if they are temporary artifacts, or ignored. 
I will post a patch with modified .gitignore file in a moment.
Comment 1 Eclipse Genie CLA 2016-08-01 09:11:50 EDT 
New Gerrit change created: https://git.eclipse.org/r/78259
Comment 2 Alexander Kurtakov CLA 2016-08-01 12:15:53 EDT 
I really believe these files should be produced in target/ instead of gitignoring them.
Comment 3 Eclipse Genie CLA 2020-04-16 03:19:57 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.