Here is what my build-properties folder contains but i am not sure what could be causing this to happen. I followed the tutorial. The only alteration made is the lib folder instead of libraries as there is no libraries folder within my application. the DragAndDrop jar and folders are located under the tools folder after build but the editor does not pick up on them. any help is appreciated!

2. # Create tools for the Processing open source programming language and 
3. # environment (http://www.processing.org)
4. #
5. # Customize the build properties to make the ant-build-process work for your 
6. # environment. How? Please read the comments below.
7. #
8. # The default properties are set for OSX, for Windows-settings please refer to 
9. # comments made under (1) and (2).
10. 
    
11. 
    
12. 
    
13. # (1) 
14. # Where is your Processing sketchbook located? 
15. # If you are not sure, check the sketchbook location in your Processing 
16. # application preferences.
17. # ${user.home} points the compiler to your home directory.
18. # For windows the default path to your sketchbook would be
19. # ${user.home}/My Documents/Processing (make adjustments below).
20. 
    
21. sketchbook.location=C:/Users/Cody_Short/Downloads/processing-2.0b8-windows64/processing-2.0b8
22. 
    
23. 
    
24. 
    
25. # (2) 
26. # Where are the jar files located that are required for compiling your tool such
27. # as e.g. core.jar?
28. # By default the local classpath location points to folder libs inside Eclipse's
29. # workspace (by default found in your home directory).
30. # For Windows the default path would be ${user.home}/workspace/libs (make 
31. # adjustments below).
32. 
    
33. classpath.local.location=C:/Users/Cody_Short/Downloads/processing-2.0b8-windows64/processing-2.0b8/lib
34. 
    
35. 
    
36. # For OSX users. 
37. # The following path will direct you into Processing's application source code 
38. # folder in case you put Processing inside your Applications folder. 
39. # Uncommenting the line below will overwrite the classpath.local.location from 
40. # above.
41. 
    
42. #classpath.local.location=/Applications/Processing.app/Contents/Resources/Java/lib/
43. 
    
44. 
    
45. # Add all jar files that are required for compiling your project to the local 
46. # and project classpath, use a comma as delimiter. These jar files must be 
47. # inside your classpath.local.location folder.
48. #
49. # For creating a tool, both pde.jar and core.jar are required. (pde.jar should 
50. # then be located inside folder classpath.local.location). 
51. # The best practice would be to place both, core.jar and pde.jar into your local
52. # classpath location.
53. 
    
54. classpath.local.include=pde.jar,core.jar
55. 
    
56. 
    
57. # Add processing's libraries folder to the classpath.
58. # If you don't need to include the libraries folder to your classpath, comment 
59. # out the following line.
60. 
    
61. classpath.libraries.location=${sketchbook.location}/lib
62. 
    
63. 
    
64. 
    
65. # (3)
66. # Set the java version that should be used to compile your tool.
67. 
    
68. java.target.version=1.6
69. 
    
70. 
    
71. # Set the description of the Ant build.xml file.
72. 
    
73. ant.description=ProcessingTools Ant build file.
74. 
    
75. 
    
76. 
    
77. # (4)
78. # Project details.
79. # Give your tool a name.
80. # When creating a tool, the name of the main class which implements Tool must be
81. # the same as the value defined for project.name in your build.properties.
82. 
    
83. project.name=DragAndDrop
84. 
    
85. 
    
86. # Use 'normal' or 'fast' as value for project.compile.
87. # 'fast' will only compile the project into your sketchbook.
88. # 'normal' will compile the distribution including the javadoc-reference and all
89. # web-files (the compile process here takes longer).
90. 
    
91. project.compile=normal
92. 
    
93. # All files compiled with project.compile=normal are stored 
94. # in the distribution folder.
95. 
    
96. 
    
97. 
    
98. # (5)
99. # The following items are properties that will be used to make changes to the 
100. # web document templates. Values of properties will be inserted into the 
101. # documents automatically.
102. # If you need more control, you can edit web/index.html and web/tool.properties 
103. # directly.
104. 
     
105. author.name=Cody Shor
106. author.url=http://yoururl.com
107. 
     
108. 
     
109. # Set the web page for your tool.
110. # This is NOT a direct link to where to download it.
111. 
     
112. tool.url=http://yourtoolname.com
113. 
     
114. 
     
115. # Set the category of your tool. This must be one (or many) of the following:
116. #   "3D"            "Animation"     "Compilations"      "Data"          
117. #   "Fabrication"   "Geometry"      "GUI"               "Hardware"      
118. #   "I/O"           "Language"      "Math"              "Simulation"    
119. #   "Sound"         "Utilities"     "Typography"        "Video & Vision"  
120. # If a value other than those listed is used, your tool will listed as "Other."
121. 
     
122. tool.category=Other
123. 
     
124. 
     
125. # A short sentence (or fragment) to summarize the tool's function. This will be 
126. # shown from inside the PDE when the tool is being installed. Avoid repeating 
127. # the name of your tool here. Also, avoid saying anything redundant like 
128. # mentioning that it's a tool. This should start with a capitalized letter, and 
129. # end with a period.
130. 
     
131. tool.sentence=A collection of utilities for solving this and that problem.
132. 
     
133. 
     
134. # Additional information suitable for the Processing website. The value of
135. # 'sentence' always will be prepended, so you should start by writing the
136. # second sentence here. If your tool only works on certain operating systems,
137. # mention it here.
138. 
     
139. tool.paragraph= 
140. 
     
141. 
     
142. # Set the source code repository for your project.
143. # Recommendations for storing your source code online are Google Code or GitHub.
144. 
     
145. source.host=Google Code
146. source.url=http://code.google.com/p/yourProject
147. source.repository=http://code.google.com/p/yourProject/source/browse/
148. 
     
149. 
     
150. # The current version of your tool. 
151. # This number must be parsable as an int. It increments once with each release. 
152. # This is used to compare different versions of the same tool, and check if an 
153. # update is available.
154. 
     
155. tool.version=1
156. 
     
157. 
     
158. # The version as the user will see it. 
159. # If blank, the tool.version attribute will be used here.
160. 
     
161. tool.prettyVersion=0.1.1
162. 
     
163. 
     
164. tool.copyright=(C) 2012
165. tool.dependencies=?
166. tool.keywords=?
167. 
     
168. tested.platform=osx,windows
169. tested.processingVersion=1.5
170. 
     
171. 
     
172. # Include javadoc references into your project's javadocs.
173. 
     
174. javadoc.java.href=http://java.sun.com/javase/6/docs/api/
175. javadoc.processing.href=http://processing.googlecode.com/svn/trunk/processing/build/javadoc/core/