Bob,
The debug aspect can indeed help tremendously. Willing to share with
the list a simple example of ant construct that would echo the
classpath to the console ?
Thanks
Sébastien
PS: I committed both this patch and the other one you sent for
woproject. Thanks again.
On Aug 18, 2006, at 2:07 PM, Bob Schwarzmann wrote:
> Hi,
>
> I filed an enhancement:
> http://objectstyle.org/jira/browse/WOL-253
>
> I find myself needing to know the classpath that woproject
> constructs for later use in ant. For example, findbugs uses the
> classpath to do a more exhaustive analysis. Passing a property for
> woproject to set seems like an easy way of getting this done.
> Another use would be for debugging the classpath without turning on
> the massively verbose -debug.
>
> Below is my proposed fix for review.
>
> Cheers,
> -Bob.
>
> Index: woproject/src/java/org/objectstyle/woproject/ant/WOCompile.java
> ===================================================================
> --- woproject/src/java/org/objectstyle/woproject/ant/
> WOCompile.java (revision 2998)
> +++ woproject/src/java/org/objectstyle/woproject/ant/
> WOCompile.java (working copy)
>.. -71,8 +71,17 @@
> frameworkSets.add(frameworks);
> }
>
> + private String dumpClasspath;
> +
> + public void setDumpClasspath( String dumpClasspath ){
> + this.dumpClasspath = dumpClasspath;
> + }
> +
> public void execute() throws BuildException {
> setClasspath(FrameworkSet.jarsPathForFrameworkSets
> (getProject(), frameworkSets, false));
> + if( dumpClasspath != null ){
> + getProject().setProperty( dumpClasspath, getClasspath
> ().toString() );
> + }
> super.execute();
> }
> }
>
This archive was generated by hypermail 2.0.0 : Fri Aug 18 2006 - 18:14:41 EDT