test add folder in webcontext classpath view and jetty view.

[GoogleCodeExporter]

I found that there's some issue in source scanner view about "add folder",
it's causing issue since we didn't handle project relative path well.

Related issue is Issue 109 , Issue 117 , 
and there's still a hidden issue in Issue 109 after last fixed.

I fixed all the issues in source scanner tab and tested carefully, 
but we still need to test the two other view to be sure it's not buggy anymore 
in next version.

Original issue reported on code.google.com by tonylovejava on 19 Feb 2012 at 5:56

[GoogleCodeExporter]

Tested add project for both Classpath view and Jetty View in Issue 114.  Also 
tested add custom jars to proejct and add project with/out maven dependency...

Original comment by tonylovejava on 20 Feb 2012 at 4:41

[GoogleCodeExporter]

After uncheck project in the jetty view, it's still being loaded, need to 
confirm.
(Test case:test testscanner project);

Original comment by tonylovejava on 20 Feb 2012 at 5:19

[GoogleCodeExporter]

There's a bug for container entry's real path is null,fixed at r315.

Now add project to jetty view is working properly.

Original comment by tonylovejava on 11 Mar 2012 at 4:54

[GoogleCodeExporter]

Add class-folder/jar to jetty view is working properly.

Original comment by tonylovejava on 11 Mar 2012 at 4:57

[GoogleCodeExporter]

Have to check strange behavior when two nest maven dependency in custom path.

Original comment by tonylovejava on 11 Mar 2012 at 5:40

[GoogleCodeExporter]

Fixed a bug for rendering wrong view when checked maven dependency.

Original comment by tonylovejava on 14 Mar 2012 at 4:39

[GoogleCodeExporter]

I think we have tested all case in those views.

Original comment by tonylovejava on 14 Mar 2012 at 4:57

• Changed state: Fixed