Permalink
Browse files

initial commit

  • Loading branch information...
0 parents commit 8eeb6f25c98a97cc7658a2029d5efff19b79dea7 unclebob committed Mar 26, 2010
Showing 3,229 changed files with 162,217 additions and 0 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
@@ -0,0 +1,5 @@
+*.class
+*.iml
+*.iws
+*.ipr
+
Binary file not shown.
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="var" path="JUNIT_HOME/junit.jar" sourcepath="JUNIT_SRC_HOME/junitsrc.zip"/>
+ <classpathentry kind="lib" path="lib/servlet-api.jar"/>
+ <classpathentry kind="output" path="web/WEB-INF/classes"/>
+</classpath>
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>Exercise1-NamingAndLongMethods</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>com.ibm.etools.common.migration.MigrationBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.wst.common.project.facet.core.builder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>com.ibm.etools.links.management.linksbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.wst.validation.validationbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>com.ibm.etools.webtools.validation.jsp.jspcompilationbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
+ <nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
+ </natures>
+</projectDescription>
@@ -0,0 +1,8 @@
+#Mon Dec 18 15:14:36 CST 2006
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2
+org.eclipse.jdt.core.compiler.compliance=1.4
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning
+org.eclipse.jdt.core.compiler.source=1.3
@@ -0,0 +1,4 @@
+#Mon Dec 18 10:52:20 CST 2006
+classpath.helper/org.eclipse.jdt.launching.JRE_CONTAINER\:\:org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType\:\:WebSphere\ v5.1\ Express\ JRE/owners=jst.java\:1.4
+classpath.helper/org.eclipse.jst.server.core.container\:\:com.ibm.ws.ast.st.runtime.runtimeTarget\:\:was.express.v51/owners=jst.web\:2.3
+eclipse.preferences.version=1
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project-modules id="moduleCoreId" project-version="1.5.0">
+ <wb-module deploy-name="Library">
+ <wb-resource deploy-path="/" source-path="/web"/>
+ <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
+ <property name="context-root" value="Library"/>
+ <property name="java-output-path" value="web/WEB-INF/classes"/>
+ </wb-module>
+</project-modules>
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<faceted-project>
+ <runtime name="WebSphere Application Server v5.1 Express stub"/>
+ <fixed facet="jst.java"/>
+ <fixed facet="jst.web"/>
+ <installed facet="com.ibm.websphere.extended.web" version="5.1"/>
+ <installed facet="jst.web" version="2.3"/>
+ <installed facet="com.ibm.websphere.coexistence.web" version="5.1"/>
+ <installed facet="jst.java" version="1.4"/>
+</faceted-project>
@@ -0,0 +1,15 @@
+Problems with Naming and Long Methods
+
+"Clean Code" is code that is easy to read and understand. This is
+true of the System Under Test (SUT) as well as the tests themselves.
+
+We've been getting some hints about feature enhancements to
+the Catalog and DataServices classes. Take a look at those two
+classes and their tests. Can you easily understand what is going on
+in that code? If so, go ahead and take the rest of the afternoon off.
+
+If not, then you're like most people. In this case, please open
+your refactoring toolkit and spend some time cleaning up this
+code by improving the names and any Long Methods that you find.
+Remember that a Long Method is not judged by how many lines of code,
+but rather whether or not it is doing more than one thing.
Oops, something went wrong.

0 comments on commit 8eeb6f2

Please sign in to comment.