[ 
https://jira.codehaus.org/browse/MASSEMBLY-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jörg Sesterhenn updated MASSEMBLY-665:
--------------------------------------

    Description: 
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.


  was:
Given this part of a assembly descriptor:

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

Under windows 7 this packages everything as (I) expected:

src/
  main/
    conf/
    script/
  
        
Under linux the package misses the directory 'conf':

src/
  main/
    script/


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.


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

Reply via email to