无法将 unix 可执行文件传输到目标文件夹

Question

我可以使用 maven-resources-plugin 成功地将资源文件从源复制到目标。但是在复制 unix 可执行 sh 文件时会出现问题。它是我资源下的unix可执行文件，当我双击它时成功执行。但是，在执行 "mvn clean package" 之后，它会作为文本文件而不是 unix 可执行文件传输。我不明白背后的主要原因。我试图将其作为 unix 可执行文件（如在主项目中）传输到目标文件夹中，但我找不到如何做到这一点的方法。我也不确定问题是关于 maven-resources-plugin 还是文件本身。您可以在下面看到文件的内容和我的插件配置。感谢您的帮助。

        <plugin>
           <artifactId>maven-resources-plugin</artifactId>
           <configuration>
               <delimiters>
                   <delimiter>${resource.delimiter}</delimiter>
               </delimiters>
               <useDefaultDelimiters>false</useDefaultDelimiters>
           </configuration>
           <executions>
               <execution>
                   <id>copy-resources</id>
                   <phase>compile</phase>
                   <goals>
                       <goal>copy-resources</goal>
                   </goals>
                   <configuration>
                       <outputDirectory>${project.build.directory}</outputDirectory>
                       <resources>
                           <!-- Include filtered resources and Dockerfile
                               for docker and packaging installation tests -->
                           <resource>
                               <directory>${project.basedir}/src/main/filter</directory>
                               <filtering>true</filtering>
                           </resource>
                           <resource>
                               <directory>${project.basedir}/src/main/resources</directory>
                               <filtering>true</filtering>
                               <includes>
                                   <include>application.yml</include>
                                   <include>logback.xml</include>
                               </includes>
                           </resource>
                        </resources>
                   </configuration>
               </execution>
           </executions>
       </plugin>

unix 可执行 bash 文件的内容：

          #!/bin/bash
    # 

    httpd Startup script for the Apache HTTP Server

   # chkconfig: - 85 15
   # description: Apache is a World Wide Web server.  It is used to serve \
#          HTML files and CGI.
# processname: httpd
# config: /etc/httpd/conf/httpd.conf
# config: /etc/sysconfig/httpd
# pidfile: /var/run/httpd.pid

# Source function library.
. /etc/rc.d/init.d/functions

if [ -f /etc/sysconfig/httpd ]; then
        . /etc/sysconfig/httpd
fi

# Start httpd in the C locale by default.
HTTPD_LANG=${HTTPD_LANG-"C"}

# This will prevent initlog from swallowing up a pass-phrase prompt if
# mod_ssl needs a pass-phrase from the user.
INITLOG_ARGS=""

# Set HTTPD=/usr/sbin/httpd.worker in /etc/sysconfig/httpd to use a server
# with the thread-based "worker" MPM; BE WARNED that some modules may not
# work correctly with a thread-based MPM; notably PHP will refuse to start.

# Path to the apachectl script, server binary, and short-form for messages.
apachectl=/usr/sbin/apachectl
httpd=${HTTPD-/usr/sbin/httpd}
prog=httpd
pidfile=${PIDFILE-/var/run/httpd.pid}
lockfile=${LOCKFILE-/var/lock/subsys/httpd}
RETVAL=0

# check for 1.3 configuration
check13 () {
    CONFFILE=/etc/httpd/conf/httpd.conf
    GONE="(ServerType|BindAddress|Port|AddModule|ClearModuleList|"
    GONE="${GONE}AgentLog|RefererLog|RefererIgnore|FancyIndexing|"
    GONE="${GONE}AccessConfig|ResourceConfig)"
    if LANG=C grep -Eiq "^[[:space:]]*($GONE)" $CONFFILE; then
        echo
        echo 1>&2 " Apache 1.3 configuration directives found"
        echo 1>&2 " please read /usr/share/doc/httpd-2.2.3/migration.html"
        failure "Apache 1.3 config directives test"
        echo
        exit 1
    fi
}

# The semantics of these two functions differ from the way apachectl does
# things -- attempting to start while running is a failure, and shutdown
# when not running is also a failure.  So we just do it the way init scripts
# are expected to behave here.
start() {
        echo -n $"Starting $prog: "
        check13 || exit 1
        LANG=$HTTPD_LANG daemon --pidfile=${pidfile} $httpd $OPTIONS
        RETVAL=$?
        echo
        [ $RETVAL = 0 ] && touch ${lockfile}
        return $RETVAL
}

# When stopping httpd a delay of >10 second is required before SIGKILLing the
# httpd parent; this gives enough time for the httpd parent to SIGKILL any
# errant children.
stop() {
    echo -n $"Stopping $prog: "
    killproc -p ${pidfile} -d 10 $httpd
    RETVAL=$?
    echo
    [ $RETVAL = 0 ] && rm -f ${lockfile} ${pidfile}
}
reload() {
    echo -n $"Reloading $prog: "
    if ! LANG=$HTTPD_LANG $httpd $OPTIONS -t >&/dev/null; then
        RETVAL=$?
        echo $"not reloading due to configuration syntax error"
        failure $"not reloading $httpd due to configuration syntax error"
    else
        killproc -p ${pidfile} $httpd -HUP
        RETVAL=$?
    fi
    echo
}

# See how we were called.
case "$1" in
  start)
    start
    ;;
  stop)
    stop
    ;;
  status)
        status -p ${pidfile} $httpd
    RETVAL=$?
    ;;
  restart)
    stop
    start
    ;;
  condrestart)
    if [ -f ${pidfile} ] ; then
        stop
        start
    fi
    ;;
  reload)
        reload
    ;;
  graceful|help|configtest|fullstatus)
    $apachectl $@
    RETVAL=$?
    ;;
  *)
    echo $"Usage: $prog {start|stop|restart|condrestart|reload|status|fullstatus|graceful|help|configtest}"
    exit 1
esac

exit $RETVAL

Answer 1

您可以执行以下操作，只需为您的choice via 的目录配置过滤：

<resources>
  <resource>
    <directory>src/main/filter</directory>
    <filtering>true</filtering>
  </resource>
  ...
</resources>

在 rpm maven 插件中，您可以使用以下内容：

<mapping>
  <directory>/xyz/sbin/</directory>
  <filemode>755</filemode>
  <username>user</username>
  <groupname>group</groupname>
  <sources>
    <source>
      <location>${project.build.directory}/xyz.sh</location>
    </source>
  </sources>
</mapping>

${project.build.directory} 将是target 目录。