You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by nickwallen <gi...@git.apache.org> on 2017/12/14 19:45:35 UTC
[GitHub] metron pull request #868: METRON-1351 Create Installable Packages for Ubuntu...
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/868
METRON-1351 Create Installable Packages for Ubuntu Trusty
### Changes
This PR allows us to create DEB packages to simplify the installation of Metron on a DEB-based platform like Ubuntu. I tried to follow as closely as possible the current mechanism that we use for building RPM packages.
I added an additional profile `build-debs` that allows us to build the DEBs.
```
mvn clean package -Pbuild-debs
```
There is also a fairly complete README.md that explains how the process works.
### Testing
1. Build the DEBs.
```
make clean package -DskipTests
cd metron-deployment
mvn clean package -Pbuild-debs -Pbuild-rpms
```
1. Take a look at the DEBs that were built.
```
$ find ./ -name "*.deb"
.//packaging/docker/deb-docker/target/metron-management_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-alerts_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-rest_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-maas-service_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-common_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-enrichment_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-data-management_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-parsers_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-profiler_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-config_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-elasticsearch_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-solr_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-indexing_0.4.2.deb
.//packaging/docker/deb-docker/target/metron-pcap-backend_0.4.2.deb
```
1. Install the DEBs.
```
cd packaging/docker/deb-docker
docker build -t deb-docker .
docker run -it -v `pwd`:/root deb-docker:latest /bin/bash
dpkg -i target/*.deb
```
1. Capture the contents of what is installed by all of the DEBs. Capture the output of running `tree` so that you can compare it to what the RPMs install.
I have attached the output of what I get when doing this to this PR; [ubuntu.txt](https://github.com/apache/metron/files/1560505/ubuntu.txt).
```
apt-get install tree
tree /usr/metron/0.4.2
```
```
root@4307d666c904:~# tree /usr/metron/0.4.2/
/usr/metron/0.4.2/
|-- bin
| |-- Whois_CSV_to_JSON.py
| |-- flatfile_loader.sh
| |-- geo_enrichment_load.sh
| |-- latency_summarizer.sh
| |-- maas_deploy.sh
| |-- maas_service.sh
| |-- metron-alerts-ui
| |-- metron-management-ui
| |-- metron-rest.sh
| |-- pcap_inspector.sh
| |-- pcap_query.sh
| |-- pcap_zeppelin_run.sh
| |-- prune_elasticsearch_indices.sh
| |-- prune_hdfs_files.sh
| |-- start_elasticsearch_topology.sh
| |-- start_enrichment_topology.sh
| |-- start_parser_topology.sh
| |-- start_pcap_topology.sh
| |-- start_profiler_topology.sh
| |-- start_solr_topology.sh
| |-- stellar
| |-- threatintel_bulk_prune.sh
| |-- threatintel_taxii_load.sh
| `-- zk_load_configs.sh
|-- config
| |-- elasticsearch.properties
| |-- enrichment.properties
...
221 directories, 1962 files
```
1. Take a look at the RPMs that were built previously.
```
cd ../rpm-docker
$ find ./ -name "*.rpm"
.//RPMS/noarch/metron-profiler-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-maas-service-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-rest-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-config-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-enrichment-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-pcap-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-elasticsearch-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-indexing-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-data-management-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-common-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-metron-management-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-alerts-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-solr-0.4.2-201712141550.noarch.rpm
.//RPMS/noarch/metron-parsers-0.4.2-201712141550.noarch.rpm
.//SRPMS/metron-0.4.2-201712141550.src.rpm
```
1. Install the RPMs.
```
docker build -t rpm-docker .
docker run -it -v `pwd`:/root rpm-docker:latest /bin/bash
rpm -ivh RPMS/noarch/metron-*.rpm
```
1. Capture the contents of what is installed by all of the RPMs. Capture the output of running `tree`. I have attached the output of what I get when doing this.
```
yum install tree -y
tree /usr/metron/0.4.2
```
I have attached the output of what I get when doing this to this PR; [centos.txt](https://github.com/apache/metron/files/1560504/centos.txt)).
1. Now I compare the two. In my testing, I have found that there is one extra directory on the Ubuntu/DEB side of the house; `/usr/metron/0.4.2/web/expressjs/etc`. This is just an empty directory that I believe gets stripped out when the RPMs are packaged.
```
$ diff debs.txt rpms.txt
1c1
< /usr/metron/0.4.2/
---
> /usr/metron/0.4.2
140d139
< | |-- etc
2186c2185
< 221 directories, 1962 files
---
> 220 directories, 1962 files
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/metron METRON-1351
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/868.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #868
----
commit 778cff2050769f89556182ad2eb2ed50bc9146c8
Author: Nick Allen <ni...@nickallen.org>
Date: 2017-12-13T23:27:59Z
METRON-1351 Create Installable Packages for Ubuntu Trusty
----
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
Thanks for the review @ottobackwards . I added the following JIRA to track the script updates that you mentioned.
* METRON-1383 Update Release Script to include Debian Packages
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
Done.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
Is this the first step to a bigger ubuntu story?
Are there follow on PR's lined up or planned for this that add support for an ubuntu full_dev to test if this works?
Does ambari support debs?
Will devs be expected to maintain the debs when they add to the spec file?
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
Sure. Will do.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
For the record, the outcome of the list discussion was the creation of these JIRAs that will help further enhance support of these DEB packages. These are next steps in this effort.
* METRON-1371 Enhance Mpack for Ubuntu Deployments
* METRON-1370 Create Full Dev Equivalent for Ubuntu
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
> Are there follow on PR's lined up or planned for this that add support for an ubuntu full_dev to test if this works?
Yes, I was thinking of doing something like that as a follow-on. Good thought.
> Does ambari support debs?
Yes, Ambari itself supports a variety of platforms. There will be some follow-on PRs of work I've done so that our MPack works on Ubuntu.
> Will devs be expected to maintain the debs when they add to the spec file?
There is no spec file for this, so nothing to maintain like we have to do for the RPMs.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
Works as describe, do not have a machine to test with.
Can we have some disclaimer about this not being supported until the follow ons are complete? Until there is full dev equiv. that is.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
I don't know if there is such documentation. Right now, it is understood that the rpms are nec. for full dev and ambari.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
we can update the scripts when it is 'official'
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
+1, thanks @nickwallen
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
> I am concerned that there is no documentation about having to maintain this as well as the rpms now.
There are docs here; metron-deployment/packaging/docker/deb-docker/README.md. Does that cover what you're looking for? If not, what docs in the RPM world do I need to mirror for the DEBs?
---
[GitHub] metron pull request #868: METRON-1351 Create Installable Packages for Ubuntu...
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/868#discussion_r157089695
--- Diff: metron-deployment/packaging/docker/deb-docker/pom.xml ---
@@ -0,0 +1,253 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <artifactId>metron-debs</artifactId>
+ <packaging>pom</packaging>
+ <name>metron-debs</name>
+ <version>0.4.2</version>
+ <parent>
+ <groupId>org.apache.metron</groupId>
+ <artifactId>metron-deployment</artifactId>
+ <version>0.4.2</version>
+ <relativePath>../../..</relativePath>
+ </parent>
+ <description>DEB Package Builder for Apache Metron</description>
+ <properties>
+ <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+ <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
+ <docker.tag>deb-docker</docker.tag>
+ <metron_dir>${project.parent.relativePath}/..</metron_dir>
+ </properties>
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-clean-plugin</artifactId>
+ <version>3.0.0</version>
+ <configuration>
+ <filesets>
+ <fileset>
+ <directory>target</directory>
+ <followSymlinks>false</followSymlinks>
+ <includes>
+ <include>**/*</include>
+ </includes>
+ </fileset>
+ </filesets>
+ </configuration>
+ </plugin>
+ <plugin>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>3.0.1</version>
+ <executions>
+ <execution>
+ <id>copy-deb-sources</id>
+ <phase>prepare-package</phase>
+ <goals>
+ <goal>copy-resources</goal>
+ </goals>
+ <configuration>
+ <outputDirectory>${project.basedir}/target</outputDirectory>
--- End diff --
I bring it up because my 777 had a lot of spec and copy-resource work, so remember to have do it in both places hits home ;)
---
[GitHub] metron pull request #868: METRON-1351 Create Installable Packages for Ubuntu...
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/868#discussion_r157086965
--- Diff: metron-deployment/packaging/docker/deb-docker/pom.xml ---
@@ -0,0 +1,253 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <artifactId>metron-debs</artifactId>
+ <packaging>pom</packaging>
+ <name>metron-debs</name>
+ <version>0.4.2</version>
+ <parent>
+ <groupId>org.apache.metron</groupId>
+ <artifactId>metron-deployment</artifactId>
+ <version>0.4.2</version>
+ <relativePath>../../..</relativePath>
+ </parent>
+ <description>DEB Package Builder for Apache Metron</description>
+ <properties>
+ <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+ <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
+ <docker.tag>deb-docker</docker.tag>
+ <metron_dir>${project.parent.relativePath}/..</metron_dir>
+ </properties>
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-clean-plugin</artifactId>
+ <version>3.0.0</version>
+ <configuration>
+ <filesets>
+ <fileset>
+ <directory>target</directory>
+ <followSymlinks>false</followSymlinks>
+ <includes>
+ <include>**/*</include>
+ </includes>
+ </fileset>
+ </filesets>
+ </configuration>
+ </plugin>
+ <plugin>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>3.0.1</version>
+ <executions>
+ <execution>
+ <id>copy-deb-sources</id>
+ <phase>prepare-package</phase>
+ <goals>
+ <goal>copy-resources</goal>
+ </goals>
+ <configuration>
+ <outputDirectory>${project.basedir}/target</outputDirectory>
--- End diff --
This is the same as what is in the docker rpm build, is there a way that they can share this and it doesn't have to be separately maintained?
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
I'll run this up.
I am concerned that there is no documentation about having to maintain this as well as the rpms now. Also, you should change the scripts we have the build the rpms to now build these ( like the rc-check ) maybe.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/868
Let me know if there are any outstanding concerns that were not resolved in the discuss thread. I believe this is ready unless I am forgetting something.
---
[GitHub] metron pull request #868: METRON-1351 Create Installable Packages for Ubuntu...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/868
---
[GitHub] metron pull request #868: METRON-1351 Create Installable Packages for Ubuntu...
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/868#discussion_r157089601
--- Diff: metron-deployment/packaging/docker/deb-docker/pom.xml ---
@@ -0,0 +1,253 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <artifactId>metron-debs</artifactId>
+ <packaging>pom</packaging>
+ <name>metron-debs</name>
+ <version>0.4.2</version>
+ <parent>
+ <groupId>org.apache.metron</groupId>
+ <artifactId>metron-deployment</artifactId>
+ <version>0.4.2</version>
+ <relativePath>../../..</relativePath>
+ </parent>
+ <description>DEB Package Builder for Apache Metron</description>
+ <properties>
+ <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+ <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
+ <docker.tag>deb-docker</docker.tag>
+ <metron_dir>${project.parent.relativePath}/..</metron_dir>
+ </properties>
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-clean-plugin</artifactId>
+ <version>3.0.0</version>
+ <configuration>
+ <filesets>
+ <fileset>
+ <directory>target</directory>
+ <followSymlinks>false</followSymlinks>
+ <includes>
+ <include>**/*</include>
+ </includes>
+ </fileset>
+ </filesets>
+ </configuration>
+ </plugin>
+ <plugin>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>3.0.1</version>
+ <executions>
+ <execution>
+ <id>copy-deb-sources</id>
+ <phase>prepare-package</phase>
+ <goals>
+ <goal>copy-resources</goal>
+ </goals>
+ <configuration>
+ <outputDirectory>${project.basedir}/target</outputDirectory>
--- End diff --
All I can think of is refactoring so that they both build out of the same directories ( since i don't think deb cares like rpm does ). Have the copy phase a level up or something. that get's complicated quickly too.
---
[GitHub] metron issue #868: METRON-1351 Create Installable Packages for Ubuntu Trusty
Posted by ottobackwards <gi...@git.apache.org>.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/868
That all sounds awesome, and you have obviously done a bunch on this already, which is super neat. Maybe some list discussion of what you all have in mind would be appropriate, and help avoid some of these types of questions.
---
[GitHub] metron pull request #868: METRON-1351 Create Installable Packages for Ubuntu...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/868#discussion_r157087782
--- Diff: metron-deployment/packaging/docker/deb-docker/pom.xml ---
@@ -0,0 +1,253 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <artifactId>metron-debs</artifactId>
+ <packaging>pom</packaging>
+ <name>metron-debs</name>
+ <version>0.4.2</version>
+ <parent>
+ <groupId>org.apache.metron</groupId>
+ <artifactId>metron-deployment</artifactId>
+ <version>0.4.2</version>
+ <relativePath>../../..</relativePath>
+ </parent>
+ <description>DEB Package Builder for Apache Metron</description>
+ <properties>
+ <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+ <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
+ <docker.tag>deb-docker</docker.tag>
+ <metron_dir>${project.parent.relativePath}/..</metron_dir>
+ </properties>
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-clean-plugin</artifactId>
+ <version>3.0.0</version>
+ <configuration>
+ <filesets>
+ <fileset>
+ <directory>target</directory>
+ <followSymlinks>false</followSymlinks>
+ <includes>
+ <include>**/*</include>
+ </includes>
+ </fileset>
+ </filesets>
+ </configuration>
+ </plugin>
+ <plugin>
+ <artifactId>maven-resources-plugin</artifactId>
+ <version>3.0.1</version>
+ <executions>
+ <execution>
+ <id>copy-deb-sources</id>
+ <phase>prepare-package</phase>
+ <goals>
+ <goal>copy-resources</goal>
+ </goals>
+ <configuration>
+ <outputDirectory>${project.basedir}/target</outputDirectory>
--- End diff --
Yes it is the same. I had the same thought, but could not think of a way to do it. If you or anyone has suggestions, I'd be open to improving that.
---