[
https://jira.codehaus.org/browse/MASSEMBLY-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342599#comment-342599
]
Karl Heinz Marbaise commented on MASSEMBLY-665:
-----------------------------------------------
Would you please so kind to attach a full working example to the issue or may
be a reference to a github project which would make the analysis easier. Thanks
in advance.
> OS dependent behaviour while packaging
> --------------------------------------
>
> Key: MASSEMBLY-665
> URL: https://jira.codehaus.org/browse/MASSEMBLY-665
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: sles 11 / windows 7
> Reporter: Jörg Sesterhenn
>
> Given this part of a assembly descriptor:
> {code}
> <fileSets>
> <fileSet>
> <directory>src/main/script</directory>
> <outputDirectory>bin</outputDirectory>
> <filtered>true</filtered>
> <includes>
> <include>*</include>
> </includes>
> </fileSet>
> <fileSet>
> <directory>/src/main/conf</directory>
> <outputDirectory>conf</outputDirectory>
> <includes>
> <include>*</include>
> </includes>
> </fileSet>
> </fileSets>
> {code}
> Under windows 7 this packages everything as (I) expected:
> {code}
> src/
> main/
> conf/
> script/
> {code}
>
> Under linux the package misses the directory 'conf':
> {code}
> src/
> main/
> script/
> {code}
> Linux seems to interpret the directory as absolute path due to the leading
> slash.
> Please either
> * accept the above config and build the same package on any system, or
> * fail the build with an invalid descriptor error, or
> * (at least) log a warning that due to the config builds are depending on the
> OS.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
