[jira] Updated: (MAVEN-1677) "No directory specified for fileset" when debugging for org.apache.commons.jelly.tags.ant.AntTag on

["Arnaud Heritier (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MAVEN-1677?page=all ]

Arnaud Heritier updated MAVEN-1677:
-----------------------------------

    Fix Version: 1.1-beta-3

> "No directory specified for fileset" when debugging for org.apache.commons.jelly.tags.ant.AntTag on
> ---------------------------------------------------------------------------------------------------
>
>          Key: MAVEN-1677
>          URL: http://jira.codehaus.org/browse/MAVEN-1677
>      Project: Maven
>         Type: Bug

>   Components: jelly/ant integration
>     Versions: 1.1-beta-1
>  Environment: OS X 10.4.2, java version "1.5.0_02"
>     Reporter: Scott Lamb
>     Priority: Minor
>      Fix For: 1.1-beta-3

>
>
> I've been trying to debug problems by specifying an alternate log4j.configuration:
>     $ MAVEN_OPTS="-Dlog4j.configuration=file:$HOME/log4j.properties" maven
> In the process, I discovered that when the level for org.apache.commons.jelly.tags.ant.AntTag is set to DEBUG, maven yields this error:
>     File...... ${1}
>     Element... ant:fileset
>     Line...... 49
>     Column.... 45
>     No directory specified for fileset.
> When logging for that class is at INFO level, this error does not occur.
> This happens on the "java:compile" goal of even the simplest project. I can attach full exception info, the project I used, and the log4j config file I used if desired.
> I'd like to figure out what jelly file this occurred in. The file "${1}" is not too helpful, though.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira