[ 
https://issues.apache.org/jira/browse/MRESOURCES-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438937#comment-16438937
 ] 

george commented on MRESOURCES-246:
-----------------------------------

I just want to copy the excel file to output directory, do not modify the 
content of the file,

here is the pom config:
{code:java}
<plugin>
    <artifactId>maven-resources-plugin</artifactId>
    <executions>
        <execution>
            <id>copy-resources</id>
            <phase>validate</phase>
            <goals>
                <goal>copy-resources</goal>
            </goals>
            <configuration>
                
<outputDirectory>${project.build.directory}/resources</outputDirectory>
                <resources>
                    <resource>
                        <directory>src/main/resources</directory>
                        <!--<filtering>true</filtering>-->
                    </resource>
                </resources>
            </configuration>
        </execution>
    </executions>
</plugin>
{code}
here if I commented the "filtering" config, the file which copied to output 
directory is OK; but if I set filtering = true, the file is broken

> set filtering = true will make some excel file to be broken
> -----------------------------------------------------------
>
>                 Key: MRESOURCES-246
>                 URL: https://issues.apache.org/jira/browse/MRESOURCES-246
>             Project: Maven Resources Plugin
>          Issue Type: Bug
>          Components: filtering
>    Affects Versions: 3.0.2
>            Reporter: george
>            Assignee: Robert Scholte
>            Priority: Major
>         Attachments: QQ截图20180414171050.png, QQ截图20180414171103.png, 
> export.xlsx
>
>
> while I set filtering = true, maven-resources-plugin will copy my excel file 
> to the directory, but the file is broken, can be opened,
> after I set filtering = false, or comment this line of settings, the file is 
> ok,
> I use maven-kotlin-plugin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to