- * Ways to fix path problem: 1) find a path to WEB-INF directory based on\r
- * the path to a known class. Then prepend this absolute path to the rest of\r
- * paths pros: no input from user cons: relocation of the source may cause\r
- * problems 2) Require users to add configuration directories to the class\r
- * path and then load entries from it. pros: cons: Many paths needs to be\r
- * added. Put significant burden on the user. Hard to tell web appl server\r
- * to add these entries to its class path. 3) Ask for project source\r
- * directory explicitly in the configuration. pros cons: similar to 1, but\r
- * this initial configuration file must reside in well known location! Why\r
- * ask users what can be found automatically? 4) Have everything in the\r
- * location already in class path for tomcat. cons: only classes and\r
- * lib/*.jar are added, eclipse will remove non classses from classes dir.\r
+ * Ways to fix path problem: \r
+ * 1) find a path to WEB-INF directory based on the path to a known class. \r
+ * Then prepend this absolute path to the rest of paths \r
+ * pros: no input from user \r
+ * cons: relocation of the source may cause problems \r
+ * \r
+ * 2) Require users to add configuration directories to the class\r
+ * path and then load entries from it. \r
+ * pros: \r
+ * cons: Many paths needs to be added. Put significant burden on the user. \r
+ * Hard to tell web appl server to add these entries to its class path. \r
+ * \r
+ * 3) Ask for project source directory explicitly in the configuration. \r
+ * pros:\r
+ * cons: similar to 1, but this initial configuration file must reside in \r
+ * well known location! Why ask users what can be found automatically?\r
+ * \r
+ * 4) Have everything in the location already in class path for tomcat. \r
+ * pros:\r
+ * cons: only classes and lib/*.jar are added, Eclipse will remove non \r
+ * classses from classes dir.\r