Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 35408 invoked from network); 11 Jan 2010 21:12:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Jan 2010 21:12:34 -0000 Received: (qmail 18372 invoked by uid 500); 11 Jan 2010 21:12:33 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 18298 invoked by uid 500); 11 Jan 2010 21:12:33 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 18285 invoked by uid 99); 11 Jan 2010 21:12:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 21:12:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of david.blevins@visi.com designates 208.42.176.212 as permitted sender) Received: from [208.42.176.212] (HELO g2host.com) (208.42.176.212) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 21:12:25 +0000 Received: from [217.203.100.110] (account dblevins@visi.com [217.203.100.110] verified) by mailfront1.g2host.com (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 134804764 for dev@geronimo.apache.org; Mon, 11 Jan 2010 15:11:59 -0600 Message-Id: From: David Blevins To: dev@geronimo.apache.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: project with server-assembly packaging Date: Mon, 11 Jan 2010 22:11:54 +0100 X-Mailer: Apple Mail (2.936) Attempting to resuscitate the failover demo. I've gotten it to go if I use 2.2-SNAPSHOT for everything, but attempting to bump it up to the released 2.2 jars creates some issues. First one seems like a general issue with our custom server-assembly packaging type. If the pom.version of the project declaring itself a server-assembly does not match the target Geronimo version, then the chain of dependencies seems to break down a bit: I've switched the geronimo-tomcat-farm-controller's version to 5.4- SNAPSHOT just to illustrate: [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Geronim Plugin Farm Controller Server Assembly for Tomcat [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean] [INFO] [genesis:validate-configuration {execution: default}] [...] Missing: ---------- 1) org.apache.geronimo.testsupport:testsupport-common:jar:5.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file - DgroupId=org.apache.geronimo.testsupport -DartifactId=testsupport- common -Dversion=5.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file - DgroupId=org.apache.geronimo.testsupport -DartifactId=testsupport- common -Dversion=5.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file - Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.assemblies:geronimo-tomcat-farm- controller:server-assembly:5.4-SNAPSHOT 2) org.apache.geronimo.testsupport:testsupport-common:jar:5.4- SNAPSHOT ---------- 1 required artifact is missing. for artifact: org.apache.geronimo.assemblies:geronimo-tomcat-farm- controller:server-assembly:5.4-SNAPSHOT I could call the assembly 2.2 as well but that seems like a terrible hack as I will be needing to update this demo quite a bit -- not that it works if I do that anyway. I can get it to work if I build that latest, pre-release, 2.2-SNAPSHOT of geronimo locally and change the demo version to 2.2-SNAPSHOT as well, so I know we're otherwise in good shape and just need to work through some tooling issues. I'd sort of prefer to rip the band-aid off now rather than just put it off till later. Anyway, any ideas on what happens to the dependency tree that causes a server-assembly to get a dep on the testsupport-common-$ {notTheGeronimoVersion}.jar ? -David