From 560d5f75fed8bb44df915140c74512c7d95d1717 Mon Sep 17 00:00:00 2001
From: Stanislav Ochotnicky <sochotnicky@redhat.com>
Date: Tue, 27 Mar 2012 10:11:41 +0200
Subject: [PATCH 6/8] Remove unpack-config-deps from distribution

This is needed because original code used classifiers to select subset
of artifacts. Unfortunately there seems to be a weird bug affecting even
upstream maven when this goes outside of reactor resolver. Or perhaps
this is a weird feature.

Our resolver obviously can't handle this so we have to unpack these
manually before building distribution
---
 jetty-distribution/pom.xml |   14 --------------
 1 files changed, 0 insertions(+), 14 deletions(-)

diff --git a/jetty-distribution/pom.xml b/jetty-distribution/pom.xml
index aff91ff..8cd3aba 100644
--- a/jetty-distribution/pom.xml
+++ b/jetty-distribution/pom.xml
@@ -202,20 +202,6 @@
             </configuration>
           </execution>
           <execution>
-            <id>unpack-config-deps</id>
-            <phase>generate-resources</phase>
-            <goals>
-              <goal>unpack-dependencies</goal>
-            </goals>
-            <configuration>
-              <includeGroupIds>org.eclipse.jetty</includeGroupIds>
-              <classifier>config</classifier>
-              <failOnMissingClassifierArtifact>false</failOnMissingClassifierArtifact>
-              <excludes>META-INF/**</excludes>
-              <outputDirectory>${assembly-directory}</outputDirectory>
-            </configuration>
-          </execution>
-          <execution>
             <id>copy-lib-monitor-deps</id>
             <phase>generate-resources</phase>
             <goals>
-- 
1.7.7.6