From c20556699d33e3a85329650d9ef21f17190ecf0f 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/6] 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 bb6aff6..00101d0 100644

--- a/jetty-distribution/pom.xml

+++ b/jetty-distribution/pom.xml

@@ -216,20 +216,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>unpack-javadoc</id>

             <phase>generate-resources</phase>

             <goals>

-- 

1.7.9