\todoin{Write}
\chapter{Eclipse Bugs Found}
-\todoin{Add other things and change headline?}
+\newcommand{\submittedBugReport}[1]{The submitted bug report can be found on
+ \url{#1}.}
\section{Eclipse bug 420726: Code is broken when moving a method that is
assigning to the parameter that is also the move
destination}\label{eclipse_bug_420726}
-This bug\footnote{\url{https://bugs.eclipse.org/bugs/show\_bug.cgi?id=420726}}
+This bug
was found when analyzing what kinds of names that was to be considered as
\emph{unfixes} \see{unfixes}.
variable and also is assigned to within the method body. \name{Eclipse} allows this to
happen, although it is the sure path to a compilation error. This is because we
would then have an assignment to a \var{this} expression, which is not allowed
-in Java.
+in Java.
+\submittedBugReport{https://bugs.eclipse.org/bugs/show\_bug.cgi?id=420726}
\subsection{The solution}
The solution to this problem is to add all simple names that are assigned to in
\section{Eclipse bug 429416: IAE when moving method from anonymous
class}\label{eclipse_bug_429416}
-I
-discovered\footnote{\url{https://bugs.eclipse.org/bugs/show\_bug.cgi?id=429416}}
+I discovered
this bug during a batch change on the \type{org.eclipse.jdt.ui} project.
\subsection{The bug}
a name, hence the term \emph{anonymous} class! Therefore, when its name, an
empty string, is passed into
\methodwithref{org.eclipse.jdt.core.dom.AST}{newSimpleName} it all ends in an
-\type{IllegalArgumentException}.
+\type{IllegalArgumentException}.
+\submittedBugReport{https://bugs.eclipse.org/bugs/show\_bug.cgi?id=429416}
\subsection{How I solved the problem}
Since the \type{MoveInstanceMethodProcessor} is instantiated in the
\section{Eclipse bug 429954: Extracting statement with reference to local type
breaks code}\label{eclipse_bug_429954}
-The bug\footnote{\url{https://bugs.eclipse.org/bugs/show\_bug.cgi?id=429954}}
+The bug
was discovered when doing some changes to the way unfixes is computed.
\subsection{The bug}
local types to be extracted. When this happens the code is broken, since the
extracted method must take a parameter of a local type that is not in the
methods scope. The problem is illustrated in
-\myref{lst:extractMethod_LocalClass}, but there in another setting.
+\myref{lst:extractMethod_LocalClass}, but there in another setting.
+\submittedBugReport{https://bugs.eclipse.org/bugs/show\_bug.cgi?id=429954}
\subsection{Actions taken}
There are no actions directly springing out of this bug, since the Extract