I am e beginner

[Nelson]

hi!
I had discovered Glean and I wanted using this application.
so I downlded the glean file.
with the windows console i went ino the directory and i tape ant -
download-tools
an error message appear

BUILD FAILED
C:\Nelson\TestOutils\glean-1.3\build.xml:129: The following error
occurred while
executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:17: Could not create task
or type o
f type: antlib:org.apache.maven.artifact.ant:remoteRepository.

Ant could not find the task or a class this task relies upon.

My configuration is:
ant 1.6.5
j2sdk1.4.2_16
ANT_HOME=C:\ant-1.6.5
JAVA_HOME=C:\j2sdk1.4.2_16
path= ....... %ANT_HOME%\bin;%JAVA_HOME%\bin
I have a proxy

so into the build.xml I add

<target name="download-tools"
description="Download the set of tools with scripts for
Glean">
<property name="proxy.port" value="vvv"/>
<property name="proxy.host" value="vvv"/>
<property name="proxy.pass" value="vvv"/>
<property name="proxy.user" value="vv"/>
<setproxy
proxyhost="${proxy.host}"
proxyport="${proxy.port}"
proxyuser="${proxy.user}"
proxypassword="${proxy.pass}"
/>
<ant antfile="get-tools.xml" target="all"/>
</target>
thx

[John Brugge]

I'm going to guess that you need to install the Ant Tasks For Maven (http://maven.apache.org/ant-tasks.html). That script uses them to grab some of the tools from various Maven repositories. I considered adding to the script so that it would try to download and install the Ant Tasks for Maven that are needed first (that is, bootstrap the whole thing), but I wanted to get a basic script working first.

So if you follow the download link on the Ant Tasks for Maven page, and put the JAR file in your (Ant home)/lib directory (or, alternatively, in your (user home)/.ant/lib directory), then the "ant download-tools" script should work.

And I'll add to my to-do list to add in support for proxies to that script as well.

Let me know if you still run in to trouble,
John

[Nelson]

Thank you.
Now it is trying to work.
In fact there is an other problem which occure when it try to do the
beandoc's task.
I suppose that glean try to connect into that URL
http://repo1.maven.org/maven2/springframework/
ant the spring-beandoc directory doesn't exist!
that's why I have:
init:
[echo] **** Writing tool home properties to C:/Nelson/TestOutils/
glean-1.3/
toolhome.properties.local
[echo] **** Copy this file to the Glean home directory when
finished.

beandoc:
[artifact:dependencies] Downloading: org/springframework/spring-
beandoc/0.8.1/sp
ring-beandoc-0.8.1.pom from repo1.repository
[artifact:dependencies] Downloading: org/springframework/spring-
beandoc/0.8.1/sp
ring-beandoc-0.8.1.pom from central
[artifact:dependencies] Downloading: org/springframework/spring-
beandoc/0.8.1/sp
ring-beandoc-0.8.1.jar from repo1.repository
[artifact:dependencies] Downloading: org/springframework/spring-
beandoc/0.8.1/sp
ring-beandoc-0.8.1.jar from central
[artifact:dependencies] An error has occurred while processing the
Maven artifac
t tasks.
[artifact:dependencies] Diagnosis:
[artifact:dependencies]
[artifact:dependencies] Unable to resolve artifact: Missing:
[artifact:dependencies] ----------
[artifact:dependencies] 1) org.springframework:spring-beandoc:jar:
0.8.1
[artifact:dependencies]
[artifact:dependencies] Try downloading the file manually from the
project web
site.
[artifact:dependencies]
[artifact:dependencies] Then, install it using the command:
[artifact:dependencies] mvn install:install-file -
DgroupId=org.springframe
work -DartifactId=spring-beandoc -Dversion=0.8.1 -Dpackaging=jar -
Dfile=/path/to
/file
[artifact:dependencies]
[artifact:dependencies] Alternatively, if you host your own
repository you can
deploy the file there:
[artifact:dependencies] mvn deploy:deploy-file -
DgroupId=org.springframewo
rk -DartifactId=spring-beandoc -Dversion=0.8.1 -Dpackaging=jar -Dfile=/
path/to/f
ile -Durl=[url] -DrepositoryId=[id]
[artifact:dependencies]
[artifact:dependencies] Path to dependency:
[artifact:dependencies] 1) org.apache.maven:super-pom:jar:2.0
[artifact:dependencies] 2) org.springframework:spring-
beandoc:jar:0.8.1
[artifact:dependencies]
[artifact:dependencies] ----------
[artifact:dependencies] 1 required artifact is missing.
[artifact:dependencies]
[artifact:dependencies] for artifact:
[artifact:dependencies] org.apache.maven:super-pom:jar:2.0
[artifact:dependencies]
[artifact:dependencies] from the specified remote repositories:
[artifact:dependencies] repo1.repository (http://repo1.maven.org/
maven2),
[artifact:dependencies] central (http://repo1.maven.org/maven2)
[artifact:dependencies]
[artifact:dependencies]

BUILD FAILED
C:\Nelson\TestOutils\glean-1.3\build.xml:131: The following error

occurred while
executing this line:

C:\Nelson\TestOutils\glean-1.3\get-tools.xml:84: The following error
occurred wh
ile executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:37: The following error
occurred wh
ile executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:52: Unable to resolve
artifact: Mis
sing:
----------
1) org.springframework:spring-beandoc:jar:0.8.1

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.springframework -
DartifactId=spring
-beandoc -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the
file there:

mvn deploy:deploy-file -DgroupId=org.springframework -
DartifactId=spring-b
eandoc -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file -
Durl=[url] -Dreposi
toryId=[id]

Path to dependency:
1) org.apache.maven:super-pom:jar:2.0
2) org.springframework:spring-beandoc:jar:0.8.1

----------
1 required artifact is missing.

for artifact:
org.apache.maven:super-pom:jar:2.0

from the specified remote repositories:
repo1.repository (http://repo1.maven.org/maven2),
central (http://repo1.maven.org/maven2)

What I should do?
Download manually spring-beandoc-0.8.1-bin.zip that file, extract
spring-beandoc-0.8.1.jar into ..\tools\beandoc
directory and then type:
mvn install:install-file -DgroupId=org.springframework -
DartifactId=spring
-beandoc -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file

I prefer to ask to someone before doing mistakes!
thx

On 6 mar, 20:31, "John Brugge" <john.bru...@gmail.com> wrote:
> I'm going to guess that you need to install the Ant Tasks For Maven (http://maven.apache.org/ant-tasks.html). That script uses them to grab some
> of the tools from various Maven repositories. I considered adding to the
> script so that it would try to download and install the Ant Tasks for Maven
> that are needed first (that is, bootstrap the whole thing), but I wanted to
> get a basic script working first.
>
> So if you follow the download link on the Ant Tasks for Maven page, and put
> the JAR file in your (Ant home)/lib directory (or, alternatively, in your
> (user home)/.ant/lib directory), then the "ant download-tools" script should
> work.
>
> And I'll add to my to-do list to add in support for proxies to that script
> as well.
>
> Let me know if you still run in to trouble,
> John
>

[Nelson]

I can add something.
I try to continue without beandoc so I blurred "bleandoc" into the all
task and I have this error message:

toolhome.properties.local
[echo] **** Copy this file to the Glean home directory when
finished.

checkstyle:
[echo] ---->C:/Nelson/TestOutils/glean-1.3/tools/checkstyle

BUILD FAILED
C:\Nelson\TestOutils\glean-1.3\build.xml:131: The following error
occurred while
executing this line:

C:\Nelson\TestOutils\glean-1.3\get-tools.xml:88: The following error

occurred wh
ile executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:37: The following error
occurred wh
ile executing this line:

C:\Nelson\TestOutils\glean-1.3\get-tools.xml:61: The <copy> type
doesn't support
the nested "path" element.
thx

On 7 mar, 11:56, Nelson <dossantos.nel...@gmail.com> wrote:
> Thank you.
> Now it is trying to work.
> In fact there is an other problem which occure when it try to do the
> beandoc's task.

> I suppose that glean try to connect into that URLhttp://repo1.maven.org/maven2/springframework/

[Nelson]

Re
I solved my second problem. Before test the glean program, I change
the beandoc version --> 0.8.1 insted of 0.7.1
But the last problem persist.

BUILD FAILED
C:\Nelson\TestOutils\glean-1.3\build.xml:131: The following error
occurred while
executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:88: The following error
occurred wh
ile executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:37: The following error
occurred wh
ile executing this line:
C:\Nelson\TestOutils\glean-1.3\get-tools.xml:61: The <copy> type
doesn't support
the nested "path" element.

I cannot continu.
Thx for your help!

[John Brugge]

My apologies - it appears that I used an Ant 1.7 feature in the get-
tools.xml script. I will look at what I can do to fix that. Until
then, you can manually download the tools that you want to use from
the links on the tools page (http://jbrugge.com/glean/tools.html).

As for the first error you were seeing, with beandoc v0.8.1, did you
update the version number in that script? I see v0.7.1 in the get-
tools.xml script. I did finally notice, though, that the Beandoc
folks have the latest version in their own Maven repo, so I'll update
the script to refer to that one.

Hope that helps,
John

[Nelson]

which java release do you use?
j2sdk 1.4
jdk5
jdk6?

[Nelson]

So now I am using
ant 1.7
JDK 5
and when I type ant -download-tools I have this pb

BUILD FAILED
C:\Nelson\TestOutils\glean-1.3\build.xml:131: The following error
occurred while
executing this line:

C:\Nelson\TestOutils\glean-1.3\get-tools.xml:16: Problem: failed to
create task
or type antlib:org.apache.maven.artifact.ant:remoteRepository
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken
place.

This appears to be an antlib declaration.
Action: Check that the implementing library exists in one of:
-C:\apache-ant-1.7.0\lib
-C:\Documents and Settings\474094\.ant\lib
-a directory added on the command line with the -lib argument

I check the ANT_HOME path, it work
but "C:\Documents and Settings\474094\.ant\lib"
doesn't work, i don't know where i can change the path

What should I do?
thx

[John Brugge]

My goal is to support JDK 1.4+, although I usually run jdk 5. If you come across things that require JDK 5 that I've missed, please let me know and I'll work on removing them.

Thanks,
John

[John Brugge]

If you had the Maven Ant tasks JAR in the Ant 1.6.5 lib folder, move them to the 1.7 lib folder. Or put them in your user.home/.ant/lib, where they'll be found by any Ant installation.

Hope that helps,
John

[John Brugge]

If you need or want to revert to Ant 1.6.5, I noticed in the Maven Ant Tasks docs that they provide a fileset reference (compatible with Ant 1.6.5's copy task) as well as a path reference for dependencies.

I'm working on getting a 1.3.1 release with this and some other fixes, but you could make this change locally for the time being if you would like.

In ${glean.home}/get-tools.xml change this:

        <!-- Download the tool and its dependencies to our local M2 repo -->
        <artifact:dependencies pathId="@{artifact}.path">
          <dependency groupID="@{group}"
            artifactID="@{artifact}"
            version="@{version}"/>
          <remoteRepository refid="@{repo}" />
        </artifact:dependencies>
       
        <!-- Copy the tool and its dependencies to a central place for Glean to use -->
        <copy todir="${tools.base}/@{artifact}-@{version}">
          <path refId="@{artifact}.path"/>
          <flattenmapper/>
        </copy>

to this:

        <!-- Download the tool and its dependencies to our local M2 repo -->
        <artifact:dependencies filesetId="@{artifact}.path">
          <dependency groupID="@{group}"
            artifactID="@{artifact}"
            version="@{version}"/>
          <remoteRepository refid="@{repo}" />
        </artifact:dependencies>
       
        <!-- Copy the tool and its dependencies to a central place for Glean to use -->
        <copy todir="${tools.base}/@{artifact}-@{version}">
          <fileset refId="@{artifact}.path"/>
          <flattenmapper/>
        </copy>

Sorry again for the inconvenience,
John

[Nelson]

thx I made a mistke, I put ant task into ant 1.6.5 lib directory
And then Glean had download some tools.
now i am trying to use glean.
So I put an ant projet.
I had into the build.xml file
<property name="glean.home" value="C:/Nelson/TestOutils/glean-1.3"/>
<property name="project.feedback.properties" value="C:/Nelson/
TestOutils/glean-1.3/testproject/feedback.properties"/>
I went into the curent directory with the windows console.
And that message appears:


C:\Nelson\TestOutils\glean-1.3\testproject>ant call-glean
Buildfile: build.xml

call-glean:

init:
[echo] Creating log directory at C:\Nelson\TestOutils\glean-1.3/
logs
[echo] Starting to gather feedback for glean-1.3 at 03-10-2008
10:22:09 AM
[echo] Feedback tools being used:
java2html14,javadoc,javancss,pmd
[echo] Collector tools being used: none

feedback:
[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\java2
html14\build.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\java2html14\build.xml:
18:
C:\Nelson\TestOutils\glean-1.3\${tools.base}\j2h-1.3.1 not found.

init:
[echo] ++++++++ Starting javadoc at 03-10-2008 10:22:09 AM +++++++
+

javadoc:
[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\javad
oc\build.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\javadoc\build.xml:29:
C:\Nelson
\TestOutils\glean-1.3\release4\source\org\test not found.
---------> in that directory, I have packages
[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\javan
css\build.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\javancss\build.xml:
11: C:\Nelso
n\TestOutils\glean-1.3\${tools.base}\javancss-28.49 not found.
[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\pmd\b
uild.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\pmd\build.xml:11: C:
\Nelson\Tes
tOutils\glean-1.3\${tools.base}\pmd-3.9 not found.
[echo] Finished gathering feedback. Running collector tools
[echo] --->target :
[subant] No sub-builds to iterate on

check-old-dashboard-setting:

dashboard:

feedback-summary:
[xslt] Processing C:\Nelson\TestOutils\glean-1.3\glean\feedback-
summary.xml
to C:\Nelson\TestOutils\glean-1.3\glean\index.html
[xslt] Loading stylesheet C:\Nelson\TestOutils\glean-1.3\feedback-
summary.x
sl

glean:

BUILD SUCCESSFUL
Total time: 1 second


I read the error message, and then i checked that file C:\Nelson
\TestOutils\glean-1.3\glean\index.html and this file is almost empty.

thx.
Maybe ant continue to make mistakes

[John Brugge]

I'm glad to hear that you made some progress. Did you copy the
toolhome.properties.local that was generated as part of the tool
download in
to the ${glean.home} directory? It looks like it isn't resolving a
property
correctly (${tools.base}). If you did, could you send along that file
so I
could see the contents?

If you also wanted to send along your feedback.properties, I could
look at
what might be wrong with the javadoc task.

Thanks,
John

[Nelson]

It doesn't work
this is the project three:

C:\Nelson\TestOutils\glean-1.3\ --> glean dirrectory
+build.xml
+feedback.properties
-----------------------------------------------------------------------------------------------------

tool.pattern = java2html14,javadoc,javancss,pmd

collector.pattern = none

create.dashboard = false

project.root = ${basedir}

feedback.script.dir = ${basedir}

gen.report.root = ${project.root}/glean

glean.log.dir = ${feedback.script.dir}/logs

project.report.stylesheet = ${feedback.script.dir}/feedback-
summary.xsl
project.report.summary = ${gen.report.root}/feedback-summary.xml
project.report.page = ${gen.report.root}/index.html

report.css = ${feedback.script.dir}/reports.css

tool.timestamp.format = MM-dd-yyyy hh:mm:ss a

report.war.dir = ${feedback.script.dir}/target

report.deploy.dir = ${tomcat.home}/webapps

report.publish.dir = ${gen.report.root}

project.url =

####################################################
#
# Properties used by the individual reports
#
####################################################

# Default locations for source, binary, and tools
src.dir = ${project.root}/src
bin.dir = ${project.root}/bin
lib.dir = ${project.root}/lib
resources.dir = ${project.root}/src

# Default properties for an individual report.
gen.report.dir = ${gen.report.root}/${ant.project.name}
report.name = ${src.project.name}-${ant.project.name}-feedback
styled.report.name = index
report.format = xml
report.stylesheet = ${tool.basedir}/${ant.project.name}.xsl
index.page = ${styled.report.name}.html

# If your source is JDK 1.5-compliant, change this
# in your project's feedback.properties file.
source.level = 1.5

# Point this to whichever Java-to-HTML tool you have chosen
# Certain tools can use this to point their results to specific
# source files (e.g. PMD and CPD)
src.link.prefix = ../java2html14

# Default locations for test code
test.src.dir = ${project.root}/test-src
test.bin.dir = ${bin.dir}
test.lib.dir = ${lib.dir}
test.resources.dir = ${resources.dir}
test.report.dir = ${project.root}/test-results
test.fork.mode = true
test.results.pattern= TEST*.xml
unit.test.pattern = **/*Test.class

# If your project needs other JARs or folders on the classpath for
JUnit,
# define them with this property.06/25/2007 09:54:52 PM
extra.test.path =

# Certain tools need the 'dot' program from the GraphViz package
# (http://www.graphviz.org)
dot.exe = /usr/bin/dot

report.debug = false
# These are documentation properties for the tools.
# Each tool script should override these.
tool.description = 'NO DESCRIPTION AVAILABLE'
tool.min.jdk = 1.4
tool.dependencies = None
tool.url =

tool.doc.fragment = ${feedback.script.dir}/tool-table-fragment.html
----------------------------------------------------------------------------------------------------------------

+feedback-summary.xsl
+get-tools.xml
+reports.css
+test.xml
+toolhome.properties
+toolhome.properties.local

C:\Nelson\TestOutils\glean-1.3\testproject ---> ant testproject
+build.xml

+feedback.properties



----------------------------------------------------------------------------------------------------------------
tool.pattern = java2html14,javadoc,javancss,pmd

collector.pattern = none


create.dashboard = false


project.root = ${basedir}

feedback.script.dir = ${basedir}


gen.report.root = ${project.root}/glean

# Override this property too change the location of the tool logs
glean.log.dir = ${feedback.script.dir}/logs

# Properties defining the report summary page
project.report.stylesheet = ${feedback.script.dir}/feedback-
summary.xsl
project.report.summary = ${gen.report.root}/feedback-summary.xml
project.report.page = ${gen.report.root}/index.html

# Define the styles available to all of the reports
report.css = ${feedback.script.dir}/reports.css

# Timestamp format used for reports and logs
tool.timestamp.format = MM-dd-yyyy hh:mm:ss a

# The output will be packaged into a WAR for easy deployment. Use this
property
# to change where you want the WAR built or sent.
report.war.dir = ${feedback.script.dir}/target


# Override this property to change the location for WAR deployment
report.deploy.dir = ${tomcat.home}/webapps

# Document root for publishing to a simple web server
report.publish.dir = ${gen.report.root}

# A project URL can be used to provide a link in the summary report
project.url =

####################################################
#
# Properties used by the individual reports
#
####################################################

# Default locations for source, binary, and tools
src.dir = ${project.root}/release4/source/org/test
bin.dir = ${project.root}/bin
lib.dir = ${project.root}/lib
resources.dir = ${project.root}/src

# Default properties for an individual report.
gen.report.dir = ${gen.report.root}/${ant.project.name}
report.name = ${src.project.name}-${ant.project.name}-feedback
styled.report.name = index
report.format = xml
report.stylesheet = ${tool.basedir}/${ant.project.name}.xsl
index.page = ${styled.report.name}.html

# If your source is JDK 1.5-compliant, change this
# in your project's feedback.properties file.
source.level = 1.4

# Point this to whichever Java-to-HTML tool you have chosen
# Certain tools can use this to point their results to specific
# source files (e.g. PMD and CPD)
src.link.prefix = ../java2html14

# Default locations for test code
test.src.dir = ${project.root}/release4/testsource
test.bin.dir = ${bin.dir}
test.lib.dir = ${lib.dir}
test.resources.dir = ${resources.dir}
test.report.dir = ${project.root}/test-results
test.fork.mode = true
test.results.pattern= TEST*.xml
unit.test.pattern = **/*Test.class

# If your project needs other JARs or folders on the classpath for
JUnit,
# define them with this property.06/25/2007 09:54:52 PM
extra.test.path =

# Certain tools need the 'dot' program from the GraphViz package
# (http://www.graphviz.org)
dot.exe = /usr/bin/dot

report.debug = false
# These are documentation properties for the tools.
# Each tool script should override these.
tool.description = 'NO DESCRIPTION AVAILABLE'
tool.min.jdk = 1.5
tool.dependencies = None
tool.url =

tool.doc.fragment = ${feedback.script.dir}/tool-table-fragment.html


----------------------------------------------------------------------------------------------------------------

+project.properties

+toolhome.properties

+toolhome.properties.local


i have the same pb
i think that my feedback.properties configuration is very bad

C:\Nelson\TestOutils\glean-1.3\testproject>ant call-glean
Buildfile: build.xml

call-glean:

[echo] --->b asedir C:\Nelson\TestOutils\glean-1.3

init:
[echo] Creating log directory at C:\Nelson\TestOutils\glean-1.3/
logs
[echo] Starting to gather feedback for glean-1.3 at 03-10-2008

04:19:21 PM

[echo] Feedback tools being used:
java2html14,javadoc,javancss,pmd
[echo] Collector tools being used: none

feedback:

[echo] --->target :
[echo] ----->basedir : C:\Nelson\TestOutils\glean-1.3
[echo] ----->project.root :
[echo] ----->src.project.name : glean-1.3
[echo] ----->feedback.timestamp : 03-10-2008 04:19:21 PM
[echo] ----->feedback.properties : C:/Nelson/TestOutils/glean-1.3/
testproje
ct/feedback.properties
[echo] ----->feedback.properties.local : C:\Nelson\TestOutils
\glean-1.3\tes
tproject\feedback.properties.local
[echo] ----->tool.classpath

[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\java2
html14\build.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\java2html14\build.xml:

18: C:\Ne
lson\TestOutils\glean-1.3\${tools.base}\j2h not found.

init:
[echo] ++++++++ Starting javadoc at 03-10-2008 04:19:21 PM +++++++

+

javadoc:
[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\javad
oc\build.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\javadoc\build.xml:29:
C:\Nelson
\TestOutils\glean-1.3\release4\source\org\test not found.

[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\javan
css\build.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\javancss\build.xml:
11: C:\Nelso

n\TestOutils\glean-1.3\${tools.base}\javancss not found.

[subant] Failure for target '' of: C:\Nelson\TestOutils
\glean-1.3\tools\pmd\b
uild.xml
[subant] The following error occurred while executing this line:
[subant] C:\Nelson\TestOutils\glean-1.3\tools\pmd\build.xml:11: C:
\Nelson\Tes

tOutils\glean-1.3\${tools.base}\pmd not found.

[echo] Finished gathering feedback. Running collector tools
[echo] --->target :

[echo] ----->basedir : C:\Nelson\TestOutils\glean-1.3
[echo] ----->project.root :
[echo] ----->src.project.name : glean-1.3
[echo] ----->feedback.timestamp : 03-10-2008 04:19:21 PM
[echo] ----->feedback.properties : C:/Nelson/TestOutils/glean-1.3/
testproje
ct/feedback.properties
[echo] ----->feedback.properties.local : C:\Nelson\TestOutils
\glean-1.3\tes
tproject\feedback.properties.local

[subant] No sub-builds to iterate on

[echo] --->b asedir C:\Nelson\TestOutils\glean-1.3

[John Brugge]

Here is an experiment you could try: create a simpler feedback.properties file for your project, starting with the one in ${glean.home}/template/sample.feedback.properties. There should be only a few properties that you need to set to get going - tool.pattern, src.dir, bin.dir, lib.dir. Other than that, the defaults are likely to at least get you something.

It's also not clear what is in your toolhome.properties.local file. That should be in ${glean.home} and should have a "tools.base = (some path)" at the top of it.

Hope that helps,
John