Uploaded image for project: 'Maven Assembly Plugin'
  1. Maven Assembly Plugin
  2. MASSEMBLY-665

OS dependent behaviour while packaging

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.4
    • 2.5.3
    • None
    • None
    • sles 11 / windows 7

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            krosenvold Kristian Rosenvold
            joerg.sesterhenn Jörg Sesterhenn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment