Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 56210 invoked from network); 13 Sep 2006 21:54:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Sep 2006 21:54:13 -0000 Received: (qmail 67053 invoked by uid 500); 13 Sep 2006 21:54:10 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 67007 invoked by uid 500); 13 Sep 2006 21:54:10 -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 66996 invoked by uid 99); 13 Sep 2006 21:54:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2006 14:54:10 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com designates 64.233.162.207 as permitted sender) Received: from [64.233.162.207] (HELO nz-out-0102.google.com) (64.233.162.207) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2006 14:54:00 -0700 Received: by nz-out-0102.google.com with SMTP id v1so1226429nzb for ; Wed, 13 Sep 2006 14:53:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=keRbnIcRiOsTyK9l6e2MCLkzn0vd/1SUiWAK9qT3hxt/N4sQK61kqMtbXDiw1dp4J/SLJqqTNLZP/ldBcd19XxTxiBx56GI4NHGgBuw2re99oZf/h15hDMJGh472fyYt6lpPUyJkYCODV/xoLv/tW1+fvl7rK9SFzQWqn+7adgc= Received: by 10.65.186.18 with SMTP id n18mr8994277qbp; Wed, 13 Sep 2006 13:03:20 -0700 (PDT) Received: from ?10.0.1.4? ( [24.7.69.241]) by mx.gmail.com with ESMTP id 1sm6986446qbh.2006.09.13.13.03.14; Wed, 13 Sep 2006 13:03:20 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <783A3445-0816-48AF-A4EF-603CB7E26436@gmail.com> References: <20060913044320.11611.qmail@web31703.mail.mud.yahoo.com> <783A3445-0816-48AF-A4EF-603CB7E26436@gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <86738727-BC34-48C6-8F36-495188435A1A@planet57.com> Content-Transfer-Encoding: 7bit From: Jason Dillon Subject: Re: Another really strange mysterious build error Date: Wed, 13 Sep 2006 13:03:04 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.2) Sender: Jason Dillon X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N AFAIK, the only was to completely isolate ourselves from these issues going forward is to have complete control over the dependencies used in the build. That means, only our repo, only artifacts which we have blessed to be used, known good pom's... and then version control/notification system when artifacts change so that we can track down when something breaks. You are absolutely right though... this is a very fragile environment... and I will even go on to say that Maven breeds fragility in larger more complicated projects. --jason On Sep 13, 2006, at 6:53 AM, Kevan Miller wrote: > I believe this problem was fixed last night by jason and david j > with an OpenEJB change to trunk/openejb2/pom.xml. The change > excludes a transitive dependency for commons-logging being pulled > in for axion. > > IIUC, maven/surefire was actively pulling in transitive > dependencies (unless excluded). In this case, when the itest was > being run the axion dependency on the old version of commons- > logging was taking precedence. > > This seems like a pretty fragile environment -- this class loading > behavior could mask problems that might exist in a true server > environment, or (as we saw here) generate unique itest problems. > Jason/David, do I have this right? How do we resolve these issues > in the future? > > --kevan > > On Sep 13, 2006, at 12:43 AM, anita kulshreshtha wrote: > >> As Jacek pointed out it is because of commons-logging jar with a >> version prior to 1.0.3. It appears that one of the source of this jar >> is geronimo-kernel! how is that possible? >> >> thanks >> Anita >> >> [INFO] >> --------------------------------------------------------------------- >> --- >> [ERROR] BUILD ERROR >> [INFO] >> --------------------------------------------------------------------- >> --- >> [INFO] Failed to resolve artifact. >> >> Missing: >> ---------- >> 1) commons-logging:commons-logging:jar:1.0 >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file -DgroupId=commons-logging >> -DartifactId=commons-lo >> gging \ >> -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file >> >> Path to dependency: >> 1) org.openejb:openejb-builder:jar:2.2-SNAPSHOT >> 2) >> org.apache.geronimo.modules:geronimo-axis-builder:jar:1.2-SNAPSHOT >> 3) org.apache.geronimo.modules:geronimo-kernel:jar:1.2- >> SNAPSHOT >> 4) commons-logging:commons-logging:jar:1.0 >> >> >> --- Jason Dillon wrote: >> >>> I see this too... have not looked into it, but we need to fix this, >>> its causing bootstrap builds of G to fail. >>> >>> --jason >>> >>> >>> On Sep 11, 2006, at 3:22 PM, David Jencks wrote: >>> >>>> I sometimes get this error building openejb-core: >>>> >>>> >>> name="org.openejb.deployment.UnpackedModuleDeploymentTest"> >>>> >>> message="org.apache.commons.logging.LogFactory.release(Ljava/lang/ >>>> ClassLoader;)V">java.lang.NoSuchMethodError: >>>> org.apache.commons.logging.LogFactory.release(Ljava/lang/ >>>> ClassLoader;)V >>>> at >>>> org.apache.geronimo.kernel.config.MultiParentClassLoader.destroy >>>> (MultiParentClassLoader.java:386) >>>> at >>>> org.apache.geronimo.kernel.classloader.JarFileClassLoader.destroy >>>> (JarFileClassLoader.java:147) >>>> at org.apache.geronimo.kernel.config.Configuration.shutdown >>> >>>> (Configuration.java:762) >>>> at org.apache.geronimo.kernel.config.Configuration.doStop >>>> (Configuration.java:742) >>>> at >>>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unload >>> >>>> (SimpleConfigurationManager.java:718) >>>> at >>>> >>> org.apache.geronimo.deployment.DeploymentConfigurationManager.unload >>>> (DeploymentConfigurationManager.java:161) >>>> at >>>> >>> >> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadCo >> n >>> >>>> figuration(SimpleConfigurationManager.java:698) >>>> at >>>> >>> >> org.apache.geronimo.deployment.DeploymentConfigurationManager.unloadC >> o >>> >>>> nfiguration(DeploymentConfigurationManager.java:157) >>>> at >>>> >>> >> org.apache.geronimo.kernel.config.SimpleConfigurationManager.unloadCo >> n >>> >>>> figuration(SimpleConfigurationManager.java:668) >>>> at >>>> >>> >> org.apache.geronimo.deployment.DeploymentConfigurationManager.unloadC >> o >>> >>>> nfiguration(DeploymentConfigurationManager.java:153) >>>> at org.apache.geronimo.deployment.DeploymentContext.close >>>> (DeploymentContext.java:364) >>>> at org.openejb.deployment.DeploymentTestSuite.setUp >>>> (DeploymentTestSuite.java:201) >>>> at org.openejb.deployment.DeploymentTestSuite.access$000 >>>> (DeploymentTestSuite.java:90) >>>> at org.openejb.deployment.DeploymentTestSuite$1.protect >>>> (DeploymentTestSuite.java:119) >>>> at junit.framework.TestResult.runProtected(TestResult.java: >>> >>>> 124) >>>> at org.openejb.deployment.DeploymentTestSuite.run >>>> (DeploymentTestSuite.java:126) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>> Method) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke >>>> (NativeMethodAccessorImpl.java:39) >>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke >>>> (DelegatingMethodAccessorImpl.java:25) >>>> at java.lang.reflect.Method.invoke(Method.java:324) >>>> at org.apache.maven.surefire.junit.JUnitTestSet.execute >>>> (JUnitTestSet.java:210) >>>> at >>>> >>> >> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes >> t >>> >>>> Set(AbstractDirectoryTestSuite.java:135) >>>> at >>>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute >>>> (AbstractDirectoryTestSuite.java:122) >>>> at >>> org.apache.maven.surefire.Surefire.run(Surefire.java:129) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>> Method) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke >>>> (NativeMethodAccessorImpl.java:39) >>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke >>>> (DelegatingMethodAccessorImpl.java:25) >>>> at java.lang.reflect.Method.invoke(Method.java:324) >>>> at >>>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess >>>> (SurefireBooter.java:225) >>>> at org.apache.maven.surefire.booter.SurefireBooter.main >>>> (SurefireBooter.java:747) >>>> >>>> >>>> >>>> I can't quite imagine how this can occur. Can anyone else? >>>> >>>> Anyway putting a try/catch block around the code to ignore the >>>> error at least lets the test pass. Should I commit this or can >>>> anyone think of a possible cause so we can actually fix it? >>>> >>>> thanks >>>> david jencks >>>> >>> >>> >> >> >> __________________________________________________ >> Do You Yahoo!? >> Tired of spam? Yahoo! Mail has the best spam protection around >> http://mail.yahoo.com >