[ 
http://jira.codehaus.org/browse/MCHECKSTYLE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266586#action_266586
 ] 

Ashok Manji commented on MCHECKSTYLE-158:
-----------------------------------------

A thought...

How can I determine whether the maven build is using the relative path 
correctly and there is not a setting elsewhere evaluating /target/images as an 
absolute path?

> Embedded error: Unable to copy static resources
> -----------------------------------------------
>
>                 Key: MCHECKSTYLE-158
>                 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-158
>             Project: Maven 2.x Checkstyle Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6
>         Environment: Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-28-server" arch: "amd64" Family: "unix"
>            Reporter: Ashok Manji
>         Attachments: rss.png_checkstyle_error.rtf
>
>
> On a local developer machine, running checkstyle completes successfully, 
> however, when running checkstyle on a server (Environment details above), the 
> following build error occurs relating to rss.png.  I cannot seem to figure 
> this out. Cleaning out the maven repository, re-downloading, going back to 
> version 2.5 makes no difference. Works locally, but not on a server.
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] An error has occurred in Checkstyle report generation.
> Embedded error: Unable to copy static resources.
> /target/images/rss.png (No such file or directory)
> [INFO] 
> ------------------------------------------------------------------------
> Attached full stacktrace to this ticket.

-- 
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

        

Reply via email to