From users-return-130885-apmail-maven-users-archive=maven.apache.org@maven.apache.org Wed Jan 23 12:45:00 2013 Return-Path: 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 5345FEA75 for ; Wed, 23 Jan 2013 12:45:00 +0000 (UTC) Received: (qmail 99062 invoked by uid 500); 23 Jan 2013 12:44:49 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 98424 invoked by uid 500); 23 Jan 2013 12:44:45 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 98394 invoked by uid 99); 23 Jan 2013 12:44:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 12:44:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of senare@gmail.com designates 209.85.217.182 as permitted sender) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 12:44:38 +0000 Received: by mail-lb0-f182.google.com with SMTP id gg6so5385319lbb.41 for ; Wed, 23 Jan 2013 04:44:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xWEdpcR5uGG/lxOwTMBmz77s5LZ3dqj2JQYAylCKc+c=; b=O7Vz+T4xv4Y+ULuRQeLPp2P2L5EatvYYtXeVroC0esOMmQfQfpbr+MKNKrVNY6g2HB XOvvFyHBGJQzbuDYrPDWy/zkiw5aq+WaCshdm78Yd8k4J3EH5lDPUHPVzPOpOLngMqL2 09DEcHgHk99pRsSN1vF++V/OJsVPq8TfKpnDnfO64GByqlFB8gssiAnssNole0cnUIDD RevNHcLGm6oO8ZByYb5lxdFLwI+OJrwlKxlYkqk2FtTOnyS5j25yoHtwcHbUTb/nbTlx UwK3A8gQ/Hxo51UgV0ASDjOY0p6wUC2isx6ROdZOEY8Oscj01yIKHMH1qpI9ZsMKrNcv G2hQ== X-Received: by 10.152.148.164 with SMTP id tt4mr1243371lab.28.1358945056444; Wed, 23 Jan 2013 04:44:16 -0800 (PST) Received: from dhcp-108.drutt.com ([192.71.49.254]) by mx.google.com with ESMTPS id b3sm8280941lbl.0.2013.01.23.04.44.15 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jan 2013 04:44:15 -0800 (PST) Message-ID: <50FFDB1E.6080905@gmail.com> Date: Wed, 23 Jan 2013 13:44:14 +0100 From: Manfred Nilsson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Maven Users List Subject: Re: Best way to retrieve multiple subsets from SVN? References: <50FFD70D.5040207@durchholz.org> In-Reply-To: <50FFD70D.5040207@durchholz.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi I am going on a hunch here what your are trying to do, in my opinion this is poorly supported by maven currently (I however guess you could use the maven-release-plugin and create a tag but I am not entirely sure that this is something that maven should solve ?) in my experience it's better to go with the solution to write down the SVN revision. And then you might whan't to look into the jenkins plugin for build-pipline but now i am just guessing what you are doing/ using ... so maybe look into one of the many articles about setting up a "build pipeline" ... here is one i found http://java.dzone.com/articles/how-build-true-pipelines Just my 5 cent :) //Manfred N On 1/23/13 1:26 PM, Joachim Durchholz wrote: > Hi all, > > I have a bunch of projects that need to extract files from an SVN > repository as part of their build process. > I need to make sure that all of them use the same SVN revision. It's > initially determined as "whatever the current HEAD is", but since HEAD > might change anytime, I need a way to make sure that all builds get > their data off the same revision number (supposed to have been the > HEAD in the near past). > > I see three approaches: > > 1) Take a snapshot of the svn repo. > The main project downloads the HEAD from SVN and publishes a zip of > the source tree. I'm not sure what the best packaging type for that is > (jar would do but it would be misleading). > The individual projects would declare the main project as a > dependency, unpack the zip, extract whatever they need, and generate > the intended artifacts. > The downside is that it involves a 460 MB upload to the public repo, > for something that's just an intermediate stage that in itself does > not have any public interest. > > 2) Just record the svn revision number. > The main project asks the SVN what's the revision number, records it > in a file, and uploads to the public repo. > The individual projects would declare the main project as a > dependency, extract the revision number, downloads whatever they need > from the SVN repo, and generate the intended artifacts. > The downside is that I don't know what the best way to store the > revision number. A properties file? Place it in the pom itself under > so that it can be used as a parent pom (that would be > nifty but I don't know whether maven can properly handle poms that > change while executing them)? > > 3) Manually record the svn revision number. > Set up a parent pom that has a revision property. Manually update that > whenever building a new snapshot. > It's simple, but creating a new snapshot requires manual intervention. > > Or maybe there's a fourth, much better way :-) > > Any advice appreciated! > > Regards, > Jo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org