Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CC13310B4F for ; Fri, 30 Aug 2013 11:05:32 +0000 (UTC) Received: (qmail 74716 invoked by uid 500); 30 Aug 2013 11:05:32 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 74565 invoked by uid 500); 30 Aug 2013 11:05:29 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 74552 invoked by uid 99); 30 Aug 2013 11:05:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 11:05:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.220.170] (HELO mail-vc0-f170.google.com) (209.85.220.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 11:05:20 +0000 Received: by mail-vc0-f170.google.com with SMTP id kw10so1232812vcb.1 for ; Fri, 30 Aug 2013 04:04:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cranton.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/BvMN8M77eUA5iEopRVE0mRXmVbkpWfWOtWB1aLCyKs=; b=MaCPcYeGOdD3Nza3+U1HzKQAbeZtpuzUMU2yJAbgOUgQgpTAH27q4fVFTpQ+i97Prs P71Ggs3PrEVLSYCG4Ly52oWG4ByjFLjWBke1Os+ZspuTik8+fLhWKnZG/Rc1wC3siYf9 rcp3+FMyowr8U48JybujG7qCLG0I4EbfrR65M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=/BvMN8M77eUA5iEopRVE0mRXmVbkpWfWOtWB1aLCyKs=; b=jID1CXxvUH6nNDD55ikVm6RwMevyhKzth5NmPST0+e1CLOWDOImynNd3PMlprFsSgc k56AD0IBg63Ito4UylSuzpSb7Hqoizsq3LXLO6C0HLKDNZrnebGUoJPeMUpBYJgiN+WS KvzeA8Q1AI0k2XgXLIaZm/J52BtpQayxCEH2SjIBYWJotIPeEP/lE3EDvzpF/W+pG1H+ Ldd0remeaKLTIuJ81SW5eHezI+7Etuw7oReA65VfhS4VO4z5QXTybPA9si17pYkOdGqm UjtatAzH5PpMGuMhAThdCdMnpRBDNz1mZOsUQz/EJrJVp8WJr2sh9Lf6x9kz/0dJW6Wh PfIQ== X-Gm-Message-State: ALoCoQk7toN62Olg20EqANWzB3J67e5nzo0FAERoiNrOo+rFrgOuHCGGmfREOZCyN9+xlwCf6ueJ MIME-Version: 1.0 X-Received: by 10.220.105.199 with SMTP id u7mr7694753vco.1.1377860678395; Fri, 30 Aug 2013 04:04:38 -0700 (PDT) Received: by 10.52.139.65 with HTTP; Fri, 30 Aug 2013 04:04:38 -0700 (PDT) X-Originating-IP: [24.128.50.227] In-Reply-To: References: <5DB47EC9AA6D4453B94E2338E5EAEFE1@gmail.com> <002a01cea553$554bc260$ffe34720$@de> Date: Fri, 30 Aug 2013 07:04:38 -0400 Message-ID: Subject: Re: [VOTE] Release Apache Camel 2.12.0 From: Scott Cranton To: dev@camel.apache.org Content-Type: multipart/alternative; boundary=047d7b343eca493aab04e5283086 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b343eca493aab04e5283086 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have one JMX unit test that runs in 2.11.1, but now fails in 2.12.0. The CamelContext.getManagementName is returning null, but only when the unit test is run as part of the larger build -- it works fine standalone. https://github.com/CamelCookbook/camel-cookbook-examples/blob/master/camel-= cookbook-monitoring/src/test/java/org/camelcookbook/monitoring/managed/Mana= gedSpringTest.java Its likely that I've got something wrong in my unit test, though I saw funny behavior in 2.11 where I had to explicitly enable the Platform MBean server (System.setProperty(JmxSystemPropertyKeys.DISABLED, "false")) otherwise the larger build would fail - that is one unit test would disable it, and spill over to other test. Again, may just be that I need to isolate my tests better... Good news is the 500+ other Camel unit tests run fine... Thoughts on what's up with that one JMX unit test? On Fri, Aug 30, 2013 at 5:51 AM, Willem jiang wrote= : > Most tests are covered by the unit tests which can be ran by Jenkins. > Now we need to run some manual test on the release candidate kit. > > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) > (English) > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: =E5=A7=9C=E5=AE=81willem > > > > > > On Friday, August 30, 2013 at 3:34 PM, Jan Mat=C3=A8rne (jhm) wrote: > > > Couldnt these tests not be automated using Jenkins or Gump? > > > > Jan > > > > > -----Urspr=C3=BCngliche Nachricht----- > > > Von: Claus Ibsen [mailto:claus.ibsen@gmail.com] > > > Gesendet: Freitag, 30. August 2013 09:26 > > > An: dev > > > Betreff: Re: [VOTE] Release Apache Camel 2.12.0 > > > > > > Hi > > > > > > I tested this release with the camel-extra source code and that worke= d > > > fine. > > > I also tried some of the examples from the Camel 2.12 distribution. > > > > > > Though have not (yet) tried any of the OSGi examples in Apache Karaf > > > 2.3.2. > > > > > > Also noticed that the doc folder holds the html of the manual. The pd= f > > > is gone which is expected. > > > So that looks good also. > > > > > > Though in the lib folder we have included camel-core-2.12.0-tests.jar > > > > > > This should IMHO be removed. Its 5.6MB and was not released previousl= y. > > > This JAR is ONLY for internal testing of Camel. Camel end users can u= se > > > the camel-xxx-test JARs for testing their Camel apps. > > > > > > This also means the size of the distro jumps from 7.4mb -> 12mb (eg > > > 2.11.1 -> 2.12.0) > > > > > > > > > > > > > > > On Wed, Aug 28, 2013 at 11:45 AM, Willem jiang willem.jiang@gmail.com)> > > > wrote: > > > > After 5 month of development, we have a new minor release candidate > > > > apache-camel-2.12.0 ready. > > > > It comes with 320 issues resolved: new features, improvements and b= ug > > > > fixes [1]. You can find the release notes here [2]. > > > > > > > > Please find the staging repo here: > > > > https://repository.apache.org/content/repositories/orgapachecamel- > > > > > > > > > 119/ > > > > > > > > The tarballs are here > > > > https://repository.apache.org/content/repositories/orgapachecamel- > > > > > > > > > 119/ > > > > org/apache/camel/apache-camel/2.12.0/ > > > > > > > > Tag: > > > > https://git-wip- > > > > > > > > > us.apache.org/repos/asf?p=3Dcamel.git;a=3Dtag;h=3Daf4c05ec6d ( > http://us.apache.org/repos/asf?p=3Dcamel.git;a=3Dtag;h=3Daf4c05ec6d) > > > > f0f1d562a8d21d0355678ca3a892d4 > > > > > > > > Please review, help out with testing and vote to approve this relea= se > > > > binary. Please mention what you tested to prevent duplicate work. > > > > > > > > > Your > > > > vote counts! > > > > > > > > [ ] +1 Release the binary as Apache Camel 2.12.0 [ ] -1 Veto the > > > > release (provide specific comments) Vote is open for at least 72 > > > > hours. > > > > > > > > Thanks in advance, > > > > Willem > > > > > > > > [1] > > > https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20CAMEL%20= AND > > > > %20fixVersion%20%3D%20%222.12.0%22 > > > > [2] > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=3D1232= 396 > > > > 8&projectId=3D12311211 > > > > > > > > > > > > > > > > -- > > > > Willem Jiang > > > > > > > > Red Hat, Inc. > > > > Web: http://www.redhat.com > > > > Blog: http://willemjiang.blogspot.com > > > > > > > > > (http://willemjiang.blogspot.com/) (English) > > > > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > > > > Twitter: willemjiang > > > > Weibo: =E5=A7=9C=E5=AE=81willem > > > > > > > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > Red Hat, Inc. > > > Email: cibsen@redhat.com (mailto:cibsen@redhat.com) > > > Twitter: davsclaus > > > Blog: http://davsclaus.com > > > Author of Camel in Action: http://www.manning.com/ibsen > > > > > > --047d7b343eca493aab04e5283086--