Return-Path: 
 <users-return-124054-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-users-archive@www.apache.org
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EE81898CE
	for <apmail-maven-users-archive@www.apache.org>;
 Wed,  2 Nov 2011 22:01:38 +0000 (UTC)
Received: (qmail 61099 invoked by uid 500); 2 Nov 2011 22:01:36 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 61029 invoked by uid 500); 2 Nov 2011 22:01:36 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 61019 invoked by uid 99); 2 Nov 2011 22:01:36 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2011 22:01:36 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of mort.motes@gmail.com designates
 209.85.216.171 as permitted sender)
Received: from [209.85.216.171] (HELO mail-qy0-f171.google.com)
 (209.85.216.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2011 22:01:28 +0000
Received: by qyk33 with SMTP id 33so7630361qyk.9
        for <users@maven.apache.org>; Wed, 02 Nov 2011 15:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=m6kjkEiFRtzwLyzRONFmmOErOTOhkZSNDaNOp1d1Xn8=;
        b=PIf/+FVg6khWu8jKrBBuaLSZXU5bTNG2dI+Hzhx02/JDaxhQ7ckUJ7vpY1aI5/H9yI
         P9VP6XthP5D2uSs96CHkXa5tkS0g2BiMBWJQFPFyQE3TLMgxsBeD1VZjTvdjvcOhDlo4
         6ZKfUnrErxM4iSku45X8xZ0zvNkIhTl2U2mPE=
MIME-Version: 1.0
Received: by 10.229.72.193 with SMTP id n1mr759877qcj.221.1320271267877; Wed,
 02 Nov 2011 15:01:07 -0700 (PDT)
Received: by 10.229.96.17 with HTTP; Wed, 2 Nov 2011 15:01:07 -0700 (PDT)
Date: Wed, 2 Nov 2011 23:01:07 +0100
Message-ID: 
 <CAA6tRY66KbVJdcBm-GbrpqOTGBhRbRgF9krPwqxOpRsK1_BoJA@mail.gmail.com>
Subject: Common build jobs for sub modules should not be executed in parent
From: motes motes <mort.motes@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

I have the following project structure:

parent
  |-> childA
  |-> childB

Is it possible to put a build task/plugin in the parent which is
common for childA and childB but should not be applied to the parent?

Eg.:

In childA and childB I have some identical build tasks using eg.
maven-antrun-plugin, maven-resources-plugin etc. and I would like to
eliminate this duplication.

I have tried to move these identical build tasks to the build scope in
the parent pom like:

<build>
...
			<plugin>
				<artifactId>maven-resources-plugin</artifactId>
				<configuration>
					<nonFilteredFileExtensions>
						<nonFilteredFileExtension>ico</nonFilteredFileExtension>
					</nonFilteredFileExtensions>
				</configuration>
				<executions>
					<execution>
						<id>copy-resources</id>
						<phase>generate-resources</phase>
						<goals>
							<goal>copy-resources</goal>
						</goals>
						<configuration>
							<outputDirectory>${data.basedir}</outputDirectory>
							<resources>
								<resource>
									<directory>data</directory>
									<filtering>true</filtering>
								</resource>
							</resources>
						</configuration>
					</execution>
					<execution>
						<id>filter-spec-file</id>
						<phase>generate-resources</phase>
						<goals>
							<goal>copy-resources</goal>
						</goals>
						<configuration>
							<outputDirectory>${basedir}</outputDirectory>
							<resources>
								<resource>
							        <filtering>true</filtering>
							        <directory>${basedir}/unfiltered</directory>
							        <includes>
							          <include>**/*.dat</include>
							        </includes>								
								</resource>
							</resources>
						</configuration>
					</execution>
				</executions>
			</plugin>
...
</build>


but it fails since it first tries to run the build plugin on the
parent which does not make sense - since its only the child modules
that have the specified files/directories.

So are there any way to remove build duplication for sub modules and
put them in a simple pom parent?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org