Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #419506 +++ The latest "dirt report" shows JDT Debug still produces "dirt" during a build. Entering 'eclipse.jdt.debug' ?? org.eclipse.jdt.debug.tests/javadebugtests.jar ?? org.eclipse.jdt.debug/jdi.jar ?? org.eclipse.jdt.debug/jdimodel.jar If these are "intermediate" files produced during the build, would be best to create them somewhere under /target so they would not cleaned up automatically during a build or rebuild.
(In reply to David Williams from comment #0) > +++ This bug was initially created as a clone of Bug #419506 +++ > > The latest "dirt report" shows JDT Debug still produces "dirt" during a > build. > > Entering 'eclipse.jdt.debug' > ?? org.eclipse.jdt.debug.tests/javadebugtests.jar > ?? org.eclipse.jdt.debug/jdi.jar > ?? org.eclipse.jdt.debug/jdimodel.jar > > If these are "intermediate" files produced during the build, would be best > to create them somewhere under /target so they would not cleaned up > automatically during a build or rebuild. Why is this now showing up, i.e. is this something new? Those files are part of the final bundle and no dirt. Note that this bundle is not JARed.
(In reply to David Williams from comment #0) > If these are "intermediate" files produced during the build, would be best > to create them somewhere under /target Are class files also produced outside the tree and not in the bin folder like in the workspace?
(In reply to Dani Megert from comment #1) > Why is this now showing up, i.e. is this something new? > > Those files are part of the final bundle and no dirt. Note that this bundle > is not JARed. Not new. In bug 419506 you mentioned "a separate bug may have to be open for debug", but one never was. (In reply to Dani Megert from comment #2) > Are class files also produced outside the tree and not in the bin folder > like in the workspace? I would guess these are produced as part of some "ant process" and (later) become part of a bundles. There's are ways of doing this "in the /target" directory (perhaps under "resources"? -- I forget) and then there is some pom incantation needed to convince Tycho to add them to the bundle ... something like "addAddtionalResources". I'd have to look for existing examples to get the exact name.
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.
Please reopen if this is still an issue.
(In reply to Dani Megert from comment #5) > Please reopen if this is still an issue. Still there. See them every time checked out I do a platform build locally, even with unmodified sources. A real pain.
(In reply to Andrey Loskutov from comment #6) > (In reply to Dani Megert from comment #5) > > Please reopen if this is still an issue. > > Still there. See them every time checked out I do a platform build locally, > even with unmodified sources. A real pain. Any help is welcome ;-)
