Hi Guillaume, The Hudson builds have been red since this change was committed - see https://builds.apache.org/job/Aries/ and https://builds.apache.org/job/Aries/1628/, the first build with the change. John and I discussed the failure on the mailing list, but I guess you missed those mails. The compilation failure is a pretty un-subtle one where an instance variable is referenced from within the owning class but doesn't exist, so I wonder if subversion somehow garbled a commit for you.
I am hoping the builds will be clean again now, but unfortunately all our build engines are offline, so we haven't had a build since I backed out the change. Holly On Tue, Aug 14, 2012 at 10:05 AM, Guillaume Nodet (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ARIES-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434009#comment-13434009 > ] > > Guillaume Nodet commented on ARIES-899: > --------------------------------------- > > It passed the hudson builds afaik, so I don't see how it could not compile. > What kind of problems do you see ? > >> Possible concurrent access to the namespace handler registry >> ------------------------------------------------------------ >> >> Key: ARIES-899 >> URL: https://issues.apache.org/jira/browse/ARIES-899 >> Project: Aries >> Issue Type: Bug >> Reporter: Guillaume Nodet >> Assignee: Guillaume Nodet >> Fix For: blueprint-core-1.0.1 >> >> > > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
