You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2003/01/14 15:15:27 UTC

[maven-bug] Created: (MAVEN-201) WINDOWS: xdoc problem (drive letter casing)

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-201


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-201
    Summary: WINDOWS: xdoc problem (drive letter casing)
       Type: Bug

     Status: Assigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: plugin-xdoc
   Versions:
             1.0-beta-8

   Assignee: Jason van Zyl
   Reporter: Charles Chan

    Created: Tue, 14 Jan 2003 8:15 AM
    Updated: Tue, 14 Jan 2003 8:15 AM
Environment: WINDOWS

Description:
another windows specific problem. This one relates to the xdoc plugin and I
have no idea how to fix it...

The self-defined tag "performJSL" (line 108) creates two patterns
(fromPattern, and toPattern) for file name transformation. The "fromPattern"
uses "${srcdir}" as part of the pattern. If maven.gen.docs is not defined,
srcdir defaults to <projectHome>/target/generated-xdocs. In Windows, the
drive letter in my project home is lower case, e.g. "c:/"

Unfortunately, fileScanner (line 119) returns path name which uses capital
case drive letter, e.g. "C:/". 

This causes the mapper.mapFileName (line 138) to fail because "c:/" doesn't
match to "C:/" and thus ${outFile} is a null string.

I can workaround this problem by defining maven.gen.docs to "C:/...." but
this should probably be fixed.

(line number might not be exact as I have been doing some debugging to reach
this conclusion)

Thanks
Charles



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira