aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John W Ross <jwr...@us.ibm.com>
Subject Re: [jira] [Commented] (ARIES-899) Possible concurrent access to the namespace handler registry
Date Tue, 14 Aug 2012 11:55:02 GMT

Hi Guillaume,

Please reference
https://builds.apache.org/job/Aries/org.apache.aries.blueprint
$org.apache.aries.blueprint.core/1631/console.

[INFO] Compilation failure

/home/jenkins/jenkins-slave/workspace/Aries/aries/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BlueprintContainerImpl.java:[107,30]
 [deprecation] org.apache.aries.blueprint.ExtendedBlueprintContainer in
org.apache.aries.blueprint has been deprecated

/home/jenkins/jenkins-slave/workspace/Aries/aries/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java:[417,8]
 cannot find symbol
symbol  : variable lock
location: class
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl

/home/jenkins/jenkins-slave/workspace/Aries/aries/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java:[425,12]
 cannot find symbol
symbol  : variable lock
location: class
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl

/home/jenkins/jenkins-slave/workspace/Aries/aries/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java:[428,12]
 cannot find symbol
symbol  : variable lock
location: class
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl

/home/jenkins/jenkins-slave/workspace/Aries/aries/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/namespace/NamespaceHandlerRegistryImpl.java:[434,16]
 cannot find symbol
symbol  : variable lock
location: class
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl


[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:715)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:556)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:535)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:387)
	at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
(DefaultLifecycleExecutor.java:348)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:180)
	at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute
(LifecycleExecutorInterceptor.java:65)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	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:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced
(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at hudson.maven.agent.Main.launch(Main.java:185)
	at hudson.maven.MavenBuilder.call(MavenBuilder.java:151)
	at hudson.maven.Maven2Builder.call(Maven2Builder.java:77)
	at hudson.maven.Maven2Builder.call(Maven2Builder.java:53)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call
(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
	at org.apache.maven.plugin.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:516)
	at org.apache.maven.plugin.CompilerMojo.execute
(CompilerMojo.java:114)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo
(DefaultPluginManager.java:490)
	at hudson.maven.agent.PluginManagerInterceptor.executeMojo
(PluginManagerInterceptor.java:182)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:694)
	... 28 more

John

"Guillaume Nodet (JIRA)" <jira@apache.org> wrote on 08/14/2012 04:05:38 AM:

> "Guillaume Nodet (JIRA)" <jira@apache.org>
> 08/14/2012 04:05 AM
>
> Please respond to
> dev@aries.apache.org
>
> To
>
> dev@aries.apache.org,
>
> cc
>
> Subject
>
> [jira] [Commented] (ARIES-899) Possible concurrent access to the
> namespace handler registry
>
>
>     [ 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
>
>
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message