From dev-return-6225-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue Sep 18 16:27:16 2007 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 21922 invoked from network); 18 Sep 2007 16:27:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Sep 2007 16:27:15 -0000 Received: (qmail 80100 invoked by uid 500); 18 Sep 2007 16:27:07 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 80074 invoked by uid 500); 18 Sep 2007 16:27:07 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 80065 invoked by uid 99); 18 Sep 2007 16:27:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 09:27:07 -0700 X-ASF-Spam-Status: No, hits=-99.8 required=10.0 tests=ALL_TRUSTED,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 16:29:00 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7FC12714212 for ; Tue, 18 Sep 2007 09:26:43 -0700 (PDT) Message-ID: <14422891.1190132803520.JavaMail.jira@brutus> Date: Tue, 18 Sep 2007 09:26:43 -0700 (PDT) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Updated: (OPENJPA-364) maven build order is incorrect In-Reply-To: <851542.1189537112043.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter updated OPENJPA-364: --------------------------------- Fix Version/s: (was: 1.0.1) This one doesn't apply to the 1.0.x stream... > maven build order is incorrect > ------------------------------ > > Key: OPENJPA-364 > URL: https://issues.apache.org/jira/browse/OPENJPA-364 > Project: OpenJPA > Issue Type: Bug > Components: build / infrastructure > Affects Versions: 1.1.0 > Reporter: Kevin Sutter > Fix For: 1.1.0 > > Attachments: OPENJPA-364-3.patch, OPENJPA-364.patch, OPENJPA-364.patch > > > From the dev mailing list. (http://www.nabble.com/order-of-build-modules-isn%27t-quite-right-tf4416976.html). > In short, we are building the aggregate jar before we have built the 1.5 modules. Details follow... BTW, this only seems to apply to the trunk (1.1.0 snapshot). > ============================================================ > > Yes, that sounds about right. This just recently started to happen... > Maybe if we create two profiles, one for 1.4 only and one for 5.0, and > just enable the appropriate one of them? This would increase > repetition (we could address that with XML entities, of course), but > might get things to run right. > - Hide quoted text - > -Patrick > On 9/10/07, Kevin Sutter wrote: > > On 9/10/07, Patrick Linskey wrote: > > > > > > > So, I'm not sure what has to change in our pom.xml files to allow one to > > > > build, package, and install our aggregrate jar on the first try. Any > > > maven > > > > experts that can help with this? > > > > > > Sadly, Marc probably knows the most, and he's on top of Mt Kilimanjaro > > > or thereabouts right now. > > > > > > Yep, and my resident build expert (Mike) is on vacation this week as well.. > > :-) > > > > Might this have started happening with the recent move from how the > > > dependencies are set up, for the purposes of keeping our mvn > > > dependencies clean? > > > > > > Yes, that sounds about right. This just recently started to happen... > > > > Kevin > > > > -Patrick > > > > > > On 9/10/07, Kevin Sutter wrote: > > > > Hi, > > > > I'm the first to admit that I'm not a maven build expert, so I'm not > > > exactly > > > > sure what needs to be changed. But, here's the problem... > > > > > > > > If I only want to build the artifacts and install them into my maven > > > > repository, I issue the following maven command. (BTW, this only > > > happens on > > > > a truly clean environment. Either just pull the contents from svn or do > > > a > > > > separate "mvn clean" first like I demonstrate below.) > > > > > > > > > mvn clean > > > > > mvn install > > > > > > > > But, when I do this, I get the following build report. Although > > > everything > > > > builds okay, look at the order of the modules getting built. We are > > > > building the aggregrate jar and distribution jars before we build kernel > > > 1.5, > > > > jpa, and jpa jdbc. Thus, the aggregrate jar that we build does not have > > > all > > > > of the required contents (because I have a clean environment to start > > > with). > > > > > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > [INFO] Reactor Summary: > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > [INFO] OpenJPA ............................................... SUCCESS [ > > > > 1.328s] > > > > [INFO] OpenJPA Utilities ..................................... SUCCESS [ > > > > 12.265s] > > > > > > > > [INFO] OpenJPA Kernel ........................................ SUCCESS [ > > > > 17.703s] > > > > > > > > [INFO] OpenJPA JDBC .......................................... SUCCESS [ > > > > 10.063s] > > > > > > > > [INFO] OpenJPA XML Store ..................................... SUCCESS [ > > > > 0.969s] > > > > [INFO] OpenJPA Aggregate Jar ................................. SUCCESS [ > > > > 17.218s] > > > > > > > > [INFO] OpenJPA Distribution .................................. SUCCESS [ > > > > 19.860s] > > > > > > > > [INFO] OpenJPA Integration Tests ............................. SUCCESS [ > > > > 0.015s] > > > > [INFO] OpenJPA Examples Integration Tests .................... SUCCESS [ > > > > 0.016s] > > > > [INFO] OpenJPA JPA TCK Integration Tests ..................... SUCCESS [ > > > > 0.016s] > > > > [INFO] OpenJPA Kernel 1.5 .................................... SUCCESS [ > > > > 0.718s] > > > > [INFO] OpenJPA JPA ........................................... SUCCESS [ > > > > 4.719s] > > > > [INFO] OpenJPA JDBC 1.5 ...................................... SUCCESS [ > > > > 0.625s] > > > > [INFO] OpenJPA JPA JDBC ...................................... SUCCESS [ > > > > 17.437s] > > > > > > > > [INFO] OpenJPA Persistence Examples .......................... SUCCESS [ > > > > 0.547s] > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > > > I looked at our pom.xml at our root level of trunk and I see the > > > following > > > > listing, which maps to the order of the build above: > > > > > > > > > > > > openjpa-lib > > > > openjpa-kernel > > > > openjpa-jdbc > > > > openjpa-xmlstore > > > > openjpa-all > > > > openjpa-project > > > > openjpa-integration > > > > > > > > > > > > The rest of our modules are listed under the jdk1.5 profile and don't > > > get > > > > built until after these 1.4 modules are built. If I re-run the exact > > > same > > > > invocation (without starting from scratch with the "mvn clean"), then > > > > everything works since the 1.5 modules are all built and pulled into the > > > > aggregrate jar. > > > > > > > > So, I'm not sure what has to change in our pom.xml files to allow one to > > > > build, package, and install our aggregrate jar on the first try. Any > > > maven > > > > experts that can help with this? > > > > > > > > Thanks, > > > > Kevin > > > > > > > > > > > > > -- > > > Patrick Linskey > > > 202 669 5907 > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.