Peter Berkman created MASSEMBLY-662:
---------------------------------------
Summary: Changing File Name Case When Using FileSets
Key: MASSEMBLY-662
URL: https://jira.codehaus.org/browse/MASSEMBLY-662
Project: Maven Assembly Plugin
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.4
Environment: Windows 7 x86 64-bit
Reporter: Peter Berkman
Attachments: dist.xml, pom.xml
I am using the Maven Assembly Plugin to build a distribution zip and am getting
some strange behavior with filename cases (which is a problem because we deploy
to Unix and Windows â issue on Unix).
POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptor>./src/main/assembly/dist.xml</descriptor>
<finalName>NG_v${project.version}_${build.date}_rev${build.number}_en_US</finalName>
<appendAssemblyId>false</appendAssemblyId>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
dist.xml:
<fileSet>
<directory>${schemas-dir}/templates/en_US</directory>
<outputDirectory>templates </outputDirectory>
</fileSet>
In the source directory, the files are ALL UPPERCASE ex: CFG_APPLICATION.XML
However, in the resulting zip file, the plugin puts them in âproper name
caseâ ex: Cfg_application.xml
Iâve searched everywhere to see if there is a content check or flag that does
this, but nothingâ¦
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira