[
https://issues.apache.org/jira/browse/AMBARI-22705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
NNN updated AMBARI-22705:
-------------------------
Description:
Files:
* ambari-funtest/pom.xml
* ambari-metrics/ambari-metrics-grafana/pom.xml
* ambari-logsearch/pom.xml
did not have the 'control' path in <build><plugins> and adding the following
solves:
<plugin>
<groupId>org.vafer</groupId>
<artifactId>jdeb</artifactId>
<version>1.0.1</version>
<executions>
<execution>
<!--Stub execution on direct plugin call - workaround for ambari
deb build process-->
<id>stub-execution</id>
<phase>none</phase>
<goals>
<goal>jdeb</goal>
</goals>
</execution>
</executions>
<configuration>
<skip>true</skip>
<attach>false</attach>
<submodules>false</submodules>
<!-- Some path like ... -->
<!--
<controlDir>${project.basedir}/../src/main/package/deb/control</controlDir> -->
<controlDir>${project.basedir}/../src/main/package/deb/control</controlDir>
</configuration>
</plugin>
when building with:
sudo mvn -B clean package jdeb:jdeb
was:
Files:
* ambari-funtest/pom.xml
* ambari-metrics/ambari-metrics-grafana/pom.xml
* ambari-logsearch/pom.xml
did not have the 'control' path in <build><plugins> and adding the following
solves:
<plugin>
<groupId>org.vafer</groupId>
<artifactId>jdeb</artifactId>
<version>1.0.1</version>
<executions>
<execution>
<!--Stub execution on direct plugin call - workaround for ambari
deb build process-->
<id>stub-execution</id>
<phase>none</phase>
<goals>
<goal>jdeb</goal>
</goals>
</execution>
</executions>
<configuration>
<skip>true</skip>
<attach>false</attach>
<submodules>false</submodules>
<controlDir>${project.basedir}/../src/main/package/deb/control</controlDir>
</configuration>
</plugin>
when building with:
sudo mvn -B clean package jdeb:jdeb
> Ambari 2.6.1 installation
> -------------------------
>
> Key: AMBARI-22705
> URL: https://issues.apache.org/jira/browse/AMBARI-22705
> Project: Ambari
> Issue Type: Bug
> Reporter: NNN
>
> Files:
> * ambari-funtest/pom.xml
> * ambari-metrics/ambari-metrics-grafana/pom.xml
> * ambari-logsearch/pom.xml
> did not have the 'control' path in <build><plugins> and adding the following
> solves:
> <plugin>
> <groupId>org.vafer</groupId>
> <artifactId>jdeb</artifactId>
> <version>1.0.1</version>
> <executions>
> <execution>
> <!--Stub execution on direct plugin call - workaround for ambari
> deb build process-->
> <id>stub-execution</id>
> <phase>none</phase>
> <goals>
> <goal>jdeb</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <skip>true</skip>
> <attach>false</attach>
> <submodules>false</submodules>
> <!-- Some path like ... -->
> <!--
> <controlDir>${project.basedir}/../src/main/package/deb/control</controlDir>
> -->
>
> <controlDir>${project.basedir}/../src/main/package/deb/control</controlDir>
> </configuration>
> </plugin>
> when building with:
> sudo mvn -B clean package jdeb:jdeb
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
