From users-return-7375-apmail-continuum-users-archive=continuum.apache.org@continuum.apache.org Thu Dec 18 17:50:14 2008 Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 9116 invoked from network); 18 Dec 2008 17:50:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Dec 2008 17:50:14 -0000 Received: (qmail 61334 invoked by uid 500); 18 Dec 2008 17:50:25 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 61310 invoked by uid 500); 18 Dec 2008 17:50:25 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 61299 invoked by uid 99); 18 Dec 2008 17:50:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2008 09:50:25 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of apache.maillist@gmail.com designates 74.125.78.146 as permitted sender) Received: from [74.125.78.146] (HELO ey-out-1920.google.com) (74.125.78.146) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2008 17:50:03 +0000 Received: by ey-out-1920.google.com with SMTP id 26so21417eyw.14 for ; Thu, 18 Dec 2008 09:49:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=WPkqONSKX65ECQo7+iM2h2uGk89R63ruf2Vljxoisrk=; b=Rn8cfkKFJJOmR6qy49I9XRUpntz6+bWoL70UVeSjUQ0U0dLfI5XlqB+b+oKMZndyA5 92UzPiaEqWB7cVi4ZMoMu85igTX1DMaWYovydClybdALXCWEQ2cPdqzPBp9OlN7A8wHt T/fBOPy8rBmc+BJFiv1FLZ7PA+276SDqocm+c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=OwOt+EPhCbfPgq9i5brjLLN+DjbvrINEyj7NOa1MPsCZ6xf9QHLz5s0wzBFfkcV++X lSwrHdAWtZzNc/eVs5HAH6FC6cPq5TFnO7X83ZaNTCnEN0H50743bHdY82eU9poJqmf4 WfAHmPBHDZiPRUBxTgDVfYfvPibNOV9D0Wc/0= Received: by 10.210.49.19 with SMTP id w19mr2620358ebw.12.1229622582509; Thu, 18 Dec 2008 09:49:42 -0800 (PST) Received: by 10.210.87.11 with HTTP; Thu, 18 Dec 2008 09:49:42 -0800 (PST) Message-ID: <61ebb7260812180949k3ab2a25bl2081368b7b6b8e80@mail.gmail.com> Date: Thu, 18 Dec 2008 09:49:42 -0800 From: "L. J." To: users@continuum.apache.org Subject: Re: Multiple modules project and Continuum 1.2.2 In-Reply-To: <21074027.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_35788_33494361.1229622582495" References: <21060827.post@talk.nabble.com> <61ebb7260812171609n51fcefb1s15afcec4e0c01fd3@mail.gmail.com> <21073295.post@talk.nabble.com> <21074027.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_35788_33494361.1229622582495 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Please read thru the Maven build lifecycle http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html which you do not have to do "mvn install deploy", if you use "mvn deploy", it includes "install" as part of lifecycle. and be sure you do not use -N (--non-recursive). and yes, you have to use "deploy", Continuum does not deploy your artifacts to repository automatically as this is Maven specific task. Thanks. On Thu, Dec 18, 2008 at 6:40 AM, teacup wrote: > > It worked now. This is what I did: > > I added back only tag (mentioned in my original post) > and then used the goal 'clean install deploy'. Now Continuum deployed > artifacts for parent and all 3 children in the specified deployment > directory. > > But I would still like to know if this is the only way to deploy children > artifacts through Continuum. Thanks. > > > teacup wrote: > > > > First off I made a mistake in my original post (thanks Wendy): when I > said > > I checked the button, I meant the 'For multi modules project, load only > > root as recursive build' button and also I did not load POM from my PC > but > > specified POM URL (with user name and password). And, yes, I clicked > that > > button 'For multi modules ...'. Still I get only parent artifact > > deployed; the children artifacts still do not make it to the deployment > > directory. > > > > Then I tried the same thing after removing and > > tags from all POMs because 'Better Build with Maven' > > book says I do not need these tags if I want Continuum to deploy the > > snapshot artifacts. But this does not work either. > > > > Has anyone got children artifacts deployed through Continuum by adding > > only parent Maven 2.0 project? Would I need to add 'deploy' to the goal? > > I am using only 'clean install' because I thought Continuum would deploy > > it for me through its default config for 'Deployment Repository > > Directory'. Thanks. > > > > > > apache.maillist wrote: > >> > >> Did you check the check box "For multi modules project, load only root > as > >> recursive build"? > >> > >> On Wed, Dec 17, 2008 at 12:47 PM, teacup wrote: > >> > >>> > >>> Hello, all: > >>> > >>> I am using Continuum 1.2.2 and I have a multi-module project, with a > >>> parent > >>> POM and 3 children POM. When I upload parent POM as Maven 2.0 project > >>> and > >>> click the 'Enter the local filename of the Maven 2 POM to upload (works > >>> only > >>> for a single project without modules)' button, all loads up fine. When > I > >>> build this project recursively, everything (including site generation) > >>> works > >>> fine too, except that Continuum deploys only the parent artifact in the > >>> specified snapshots repository and none of the children artifacts make > >>> it > >>> to > >>> this repository. Here is the code from distributionManagement part > that > >>> I > >>> specify in all POM files: > >>> > >>> > >>> false > >>> internal > >>> Archiva Managed Internal Repository > >>> > >>> scp://specialuser@server > >>> :/opt/apache-tomcat-6.0.14/data/repositories/internal/ > >>> default > >>> > >>> > >>> > >>> true > >>> snapshots > >>> Archiva Managed Snapshot Repository > >>> > >>> scp://specialuser@server > >>> :/opt/apache-tomcat-6.0.14/data/repositories/snapshots/ > >>> > >>> > >>> On Continuum Admin GUI, there is a 'Configuration' button that lets you > >>> specify a 'Deployment Repository Directory' - there too I have the same > >>> snapshots directory specified like this: > >>> /opt/apache-tomcat-6.0.14/data/repositories/snapshots > >>> > >>> But nothing works, and I still cannot get Continuum deploy children > >>> artifacts under above directory. Would I need to upload and build all > 4 > >>> (1 > >>> parent and 3 children) POMs individually to get around this issue, or I > >>> am > >>> missing something in the above setup? Any help will be much > >>> appreciated. > >>> Thanks. > >>> -- > >>> View this message in context: > >>> > http://www.nabble.com/Multiple-modules-project-and-Continuum-1.2.2-tp21060827p21060827.html > >>> Sent from the Continuum - Users mailing list archive at Nabble.com. > >>> > >>> > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Multiple-modules-project-and-Continuum-1.2.2-tp21060827p21074027.html > Sent from the Continuum - Users mailing list archive at Nabble.com. > > ------=_Part_35788_33494361.1229622582495--