Re: when will the maven jira be ok

[Eric Lilja]

On 2019-08-22 04:39,  wrote:

Works fine for me, are you logged in?

https://issues.apache.org/jira/projects/MNG/summary

- Eric L


when will the maven jira be ok?
it has been down for several days.




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

when will the maven jira be ok

[????]

when will the maven jira be ok?
it has been down for several days.

Re: [VOTE] Release Apache Maven Archetype version 3.1.2

[Olivier Lamy]

+1

On Tue, 20 Aug 2019 at 21:11, Tibor Digana  wrote:

> +1
>
> On Mon, Aug 19, 2019 at 10:49 PM Tibor Digana 
> wrote:
>
> > Hi,
> >
> > We solved 9 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122=12345957
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARCHETYPE%20AND%20status%20%3D%20Open%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1527/
> >
> >
> https://repository.apache.org/service/local/repositories/maven-1527/content/org/apache/maven/archetype/maven-archetype/3.1.2/maven-archetype-3.1.2-source-release.zip
> >
> > Source release checksum(s):
> > maven-archetype-3.1.2-source-release.zip sha512:
> >
> >
> 073d5346ef8303402eb517d2764c0685b7c7885e9da02e8bcf8dc71abfb44d4fa384c737aad614e84be2905599ebdba49a0902ee07556060716cf79265b6081b
> >
> > Staging site:
> > https://maven.apache.org/archetype-archives/archetype-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > Cheers
> > Tibor17
> >
>


-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Asking for release: Eclipse 2019-06 incompatible with Tycho because of Maven 3.6.1 bug

[Tomo Suzuki]

Tibor, Thank you for following up.
I'm the author of PR#39 . I
believe the bug MRESOLVER-93
 has been in
maven-resolver for a while. Added comment in the PR summary.

On Wed, Aug 21, 2019 at 7:58 AM Enrico Olivelli  wrote:

> Il mer 21 ago 2019, 10:37 Tibor Digana  ha
> scritto:
>
> > > Is it a regression compared to last release
> >
> > This was also my question but anyway the bug looks scarying and it is an
> > indicator of hanging Maven
> > So we should ask the authour of the PR:
> > https://github.com/apache/maven-resolver/pull/39
> >
> > Cheers
> > Tibor17
> >
> > On Wed, Aug 21, 2019 at 12:39 AM Mickael Istria 
> > wrote:
> >
> > > On Tue, Aug 20, 2019 at 9:01 PM Tibor Digana 
> > > wrote:
> > >
> > > > Want to announce you about a new issue in the Resolver.
> > > > @Herve @Sylwester I found you in the history. Can you comment
> author's
> > > > changes?
> > >
> > >
> > > Is it a regression compared to last release? If not, I don't think it
> > > should be made a blocker for upcoming release.
> >
>
> I agree.
> If do not have other blocker we should cut a release as soon as possible
>
> Enrico
>
> >
> >
>


-- 
Regards,
Tomo

Re: Asking for release: Eclipse 2019-06 incompatible with Tycho because of Maven 3.6.1 bug

[Enrico Olivelli]

Il mer 21 ago 2019, 10:37 Tibor Digana  ha scritto:

> > Is it a regression compared to last release
>
> This was also my question but anyway the bug looks scarying and it is an
> indicator of hanging Maven
> So we should ask the authour of the PR:
> https://github.com/apache/maven-resolver/pull/39
>
> Cheers
> Tibor17
>
> On Wed, Aug 21, 2019 at 12:39 AM Mickael Istria 
> wrote:
>
> > On Tue, Aug 20, 2019 at 9:01 PM Tibor Digana 
> > wrote:
> >
> > > Want to announce you about a new issue in the Resolver.
> > > @Herve @Sylwester I found you in the history. Can you comment author's
> > > changes?
> >
> >
> > Is it a regression compared to last release? If not, I don't think it
> > should be made a blocker for upcoming release.
>

I agree.
If do not have other blocker we should cut a release as soon as possible

Enrico

>
>

Re: looking for some volunteer

[Tibor Digana]

Do not worry, we will prepare a branch and trigger the build process.
That's the best indicator that everything went alright.

On Wed, Aug 21, 2019 at 12:38 PM Dejan Stojadinovic 
wrote:

> @Tibor please review https://github.com/apache/maven-surefire/pull/233
>
> On 2019/05/06 13:37:02, Tibor Digana  wrote:
> > Hello Dejan, I am glad that you are back again.
> > yes, feel free. Github is yours.
> > T
> >
> > On Mon, May 6, 2019 at 2:29 PM Dejan Stojadinovic 
> > wrote:
> >
> > > This one slipped slipped though the cracks (I was few weeks off the
> grid
> > > due to traveling). Let me try to push something soon (if it is not too
> > > late).
> > >
> > > On 2019/04/07 01:19:13, Tibor Digana  wrote:
> > > > Hi Dejan,
> > > >
> > > > I almost forgot your email.
> > > > Pls create a PR on GitHub with a little work even if still
> incomplete but
> > > > at least we would not forget it.
> > > > As you can see in [1] we should create release branches and for your
> PR
> > > as
> > > > well.
> > > > [1]: https://github.com/apache/maven-surefire/pull/227
> > > >
> > > > Cheers
> > > > Tibor
> > > >
> > > >
> > > > On Tue, Mar 26, 2019 at 9:24 AM Dejan Stojadinovic <
> dejan2...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanx Tibor, I left short comments on JIRA issues (just to mark
> them).
> > > > >  I hope I will squeeze first github PR in a few days.
> > > > >
> > > > > Regards,
> > > > > Dejan
> > > > >
> > > > > On 2019/03/24 23:19:08, Tibor Digana 
> wrote:
> > > > > > Hi Dejan,
> > > > > >
> > > > > > Good to hear. In our Jira are two issues related to my original
> > > email:
> > > > > > https://issues.apache.org/jira/browse/SUREFIRE-1654
> > > > > > https://issues.apache.org/jira/browse/SUREFIRE-1494
> > > > > > If you have any questions, feel free to ask here.
> > > > > > Pls run the build locally (mvn -P run-its install) until our
> TravisCI
> > > > > build
> > > > > > would be ready for you. The build takes cca 1 hour to complete.
> > > > > > We should solve these two issue in two separate pull requests.
> > > > > > I guess these tasks require very good preparation and analysis
> of ITs
> > > > > > before making any changes.
> > > > > >
> > > > > > @Enrico can you pls investigate TravisCI, why it still behaves so
> > > much
> > > > > > differently from Jenkins CI and fails?
> > > > > > Is it really due to the deployed SNAPSHOT versions at ASF Nexus?
> > > > > >
> > > > > > Thx
> > > > > >
> > > > > > Cheers
> > > > > > Tibor
> > > > > >
> > > > > >
> > > > > > On Sun, Mar 24, 2019 at 3:23 PM Dejan Stojadinovic <
> > > dejan2...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Tibor,
> > > > > > >
> > > > > > > I volunteer for this. I have a solid experience with maven
> usage
> > > and
> > > > > also
> > > > > > > contributed few (easy) maven commits:
> > > > > > > https://github.com/apache/maven/commits?author=dejan2609
> > > > > > >
> > > > > > > Regards,
> > > > > > > Dejan Stojadinović
> > > > > > >
> > > > > > > On 2019/03/23 21:47:04, Tibor Digana 
> > > wrote:
> > > > > > > > It's going to be very pedant work for someone who want to
> help
> > > us in
> > > > > > > > Surefire.
> > > > > > > >
> > > > > > > > I am looking for some volunteer who will remove the
> deprecated
> > > config
> > > > > > > param
> > > > > > > > `forkMode` in favor of `forkCount`. All our ITs should use
> > > > > `forkCount`
> > > > > > > > since then.
> > > > > > > >
> > > > > > > > Additionally, the volunteer should deprecate
> `surefire-junit4`
> > > > > provider.
> > > > > > > > Instead `surefire-junit47` provider should be selected as
> default
> > > > > > > provider
> > > > > > > > for JUnit4 tests. Again the ITs should be changed and plugin
> > > > > dependencies
> > > > > > > > should use `surefire-junit4` provider in place where it was
> not
> > > > > > > specified.
> > > > > > > >
> > > > > > > > It's easy to do. When you see the usages of `.forkMode()`
> method
> > > -
> > > > > only
> > > > > > > 20
> > > > > > > > in `surefire-its` and 43 usages of `` in
> > > > > > > > `surefire-its/src/test/resources`.
> > > > > > > >
> > > > > > > > Successful build must prove that the changes have been
> applied
> > > > > correctly.
> > > > > > > > The changes should be in a pull request on GitHub.
> > > > > > > >
> > > > > > > > Cheers
> > > > > > > > Tibor
> > > > > > > >
> > > > > > >
> > > > > > >
> > > -
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > >
> > > > >
> > > >
> > >
> > > -
> > > To unsubscribe, 

Re: looking for some volunteer

[Dejan Stojadinovic]

@Tibor please review https://github.com/apache/maven-surefire/pull/233

On 2019/05/06 13:37:02, Tibor Digana  wrote: 
> Hello Dejan, I am glad that you are back again.
> yes, feel free. Github is yours.
> T
> 
> On Mon, May 6, 2019 at 2:29 PM Dejan Stojadinovic 
> wrote:
> 
> > This one slipped slipped though the cracks (I was few weeks off the grid
> > due to traveling). Let me try to push something soon (if it is not too
> > late).
> >
> > On 2019/04/07 01:19:13, Tibor Digana  wrote:
> > > Hi Dejan,
> > >
> > > I almost forgot your email.
> > > Pls create a PR on GitHub with a little work even if still incomplete but
> > > at least we would not forget it.
> > > As you can see in [1] we should create release branches and for your PR
> > as
> > > well.
> > > [1]: https://github.com/apache/maven-surefire/pull/227
> > >
> > > Cheers
> > > Tibor
> > >
> > >
> > > On Tue, Mar 26, 2019 at 9:24 AM Dejan Stojadinovic 
> > > wrote:
> > >
> > > > Thanx Tibor, I left short comments on JIRA issues (just to mark them).
> > > >  I hope I will squeeze first github PR in a few days.
> > > >
> > > > Regards,
> > > > Dejan
> > > >
> > > > On 2019/03/24 23:19:08, Tibor Digana  wrote:
> > > > > Hi Dejan,
> > > > >
> > > > > Good to hear. In our Jira are two issues related to my original
> > email:
> > > > > https://issues.apache.org/jira/browse/SUREFIRE-1654
> > > > > https://issues.apache.org/jira/browse/SUREFIRE-1494
> > > > > If you have any questions, feel free to ask here.
> > > > > Pls run the build locally (mvn -P run-its install) until our TravisCI
> > > > build
> > > > > would be ready for you. The build takes cca 1 hour to complete.
> > > > > We should solve these two issue in two separate pull requests.
> > > > > I guess these tasks require very good preparation and analysis of ITs
> > > > > before making any changes.
> > > > >
> > > > > @Enrico can you pls investigate TravisCI, why it still behaves so
> > much
> > > > > differently from Jenkins CI and fails?
> > > > > Is it really due to the deployed SNAPSHOT versions at ASF Nexus?
> > > > >
> > > > > Thx
> > > > >
> > > > > Cheers
> > > > > Tibor
> > > > >
> > > > >
> > > > > On Sun, Mar 24, 2019 at 3:23 PM Dejan Stojadinovic <
> > dejan2...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Tibor,
> > > > > >
> > > > > > I volunteer for this. I have a solid experience with maven usage
> > and
> > > > also
> > > > > > contributed few (easy) maven commits:
> > > > > > https://github.com/apache/maven/commits?author=dejan2609
> > > > > >
> > > > > > Regards,
> > > > > > Dejan Stojadinović
> > > > > >
> > > > > > On 2019/03/23 21:47:04, Tibor Digana 
> > wrote:
> > > > > > > It's going to be very pedant work for someone who want to help
> > us in
> > > > > > > Surefire.
> > > > > > >
> > > > > > > I am looking for some volunteer who will remove the deprecated
> > config
> > > > > > param
> > > > > > > `forkMode` in favor of `forkCount`. All our ITs should use
> > > > `forkCount`
> > > > > > > since then.
> > > > > > >
> > > > > > > Additionally, the volunteer should deprecate `surefire-junit4`
> > > > provider.
> > > > > > > Instead `surefire-junit47` provider should be selected as default
> > > > > > provider
> > > > > > > for JUnit4 tests. Again the ITs should be changed and plugin
> > > > dependencies
> > > > > > > should use `surefire-junit4` provider in place where it was not
> > > > > > specified.
> > > > > > >
> > > > > > > It's easy to do. When you see the usages of `.forkMode()` method
> > -
> > > > only
> > > > > > 20
> > > > > > > in `surefire-its` and 43 usages of `` in
> > > > > > > `surefire-its/src/test/resources`.
> > > > > > >
> > > > > > > Successful build must prove that the changes have been applied
> > > > correctly.
> > > > > > > The changes should be in a pull request on GitHub.
> > > > > > >
> > > > > > > Cheers
> > > > > > > Tibor
> > > > > > >
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > > >
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

?????? I debug the latest maven code ,find this error,anyone can help,why

[????]

I have solved this problem ,thanks .
the main class is Laucher




--  --
??: "Tibor Digana";
: 2019??8??21??(??) 4:59
??: "Maven Developers List";

: Re: I debug the latest maven code ,find this error,anyone can help,why



You are providing us with really minimum information.
So what are you debugging, what version or snapshot?
How you debug it and what's your command or test you run and what platform,
etc.
It happens only while debugging?
Ideal issues would report a bug in Jira.

On Wed, Aug 21, 2019 at 4:45 AM  <195446...@qq.com> wrote:

> [main] ERROR org.apache.maven.cli.MavenCli -
> java.util.NoSuchElementException
>   role: org.apache.maven.eventspy.internal.EventSpyDispatcher
>   roleHint:

Re: I debug the latest maven code ,find this error,anyone can help,why

[Tibor Digana]

You are providing us with really minimum information.
So what are you debugging, what version or snapshot?
How you debug it and what's your command or test you run and what platform,
etc.
It happens only while debugging?
Ideal issues would report a bug in Jira.

On Wed, Aug 21, 2019 at 4:45 AM 星光 <195446...@qq.com> wrote:

> [main] ERROR org.apache.maven.cli.MavenCli -
> java.util.NoSuchElementException
>   role: org.apache.maven.eventspy.internal.EventSpyDispatcher
>   roleHint:

I encounter this exception ,anyone can help?

[????]

1) 
org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: 
Unable to read Maven version from maven-core
  while locating org.apache.maven.execution.DefaultRuntimeInformation


at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:237)
at 
org.apache.maven.plugins.enforcer.DefaultEnforcementRuleHelper.getComponent(DefaultEnforcementRuleHelper.java:131)
at 
org.apache.maven.plugins.enforcer.DefaultEnforcementRuleHelper.getComponent(DefaultEnforcementRuleHelper.java:120)
at 
org.apache.maven.plugins.enforcer.RequireMavenVersion.execute(RequireMavenVersion.java:48)
at 
org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:193)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
Caused by: 
org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: 
Unable to read Maven version from maven-core
at 
org.apache.maven.execution.DefaultRuntimeInformation.initialize(DefaultRuntimeInformation.java:58)
at 
org.eclipse.sisu.plexus.PlexusLifecycleManager.initialize(PlexusLifecycleManager.java:303)
at 
org.eclipse.sisu.plexus.PlexusLifecycleManager.activate(PlexusLifecycleManager.java:207)
at org.eclipse.sisu.bean.BeanScheduler.schedule(BeanScheduler.java:151)
at 
org.eclipse.sisu.plexus.PlexusLifecycleManager.manage(PlexusLifecycleManager.java:147)
at 
org.eclipse.sisu.plexus.PlexusBeanBinder.afterInjection(PlexusBeanBinder.java:72)
at 
com.google.inject.internal.MembersInjectorImpl.notifyListeners(MembersInjectorImpl.java:131)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:125)
at 
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at 
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:127)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
at 
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1050)
... 46 more

Re: Asking for release: Eclipse 2019-06 incompatible with Tycho because of Maven 3.6.1 bug

[Tibor Digana]

> Is it a regression compared to last release

This was also my question but anyway the bug looks scarying and it is an
indicator of hanging Maven
So we should ask the authour of the PR:
https://github.com/apache/maven-resolver/pull/39

Cheers
Tibor17

On Wed, Aug 21, 2019 at 12:39 AM Mickael Istria  wrote:

> On Tue, Aug 20, 2019 at 9:01 PM Tibor Digana 
> wrote:
>
> > Want to announce you about a new issue in the Resolver.
> > @Herve @Sylwester I found you in the history. Can you comment author's
> > changes?
>
>
> Is it a regression compared to last release? If not, I don't think it
> should be made a blocker for upcoming release.
>

I debug the latest maven code ,find this error,anyone can help,why

[????]

Caused by: java.lang.IllegalArgumentException: Can not set 
org.apache.maven.repository.RepositorySystem field 
org.apache.maven.project.DefaultProjectBuildingHelper.repositorySystem to 
org.apache.maven.bridge.MavenRepositorySystem
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
at 
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
at java.lang.reflect.Field.set(Field.java:764)
at 
org.eclipse.sisu.bean.BeanPropertyField.set(BeanPropertyField.java:74)
at 
org.eclipse.sisu.plexus.ProvidedPropertyBinding.injectProperty(ProvidedPropertyBinding.java:48)
at 
org.eclipse.sisu.bean.BeanInjector.injectMembers(BeanInjector.java:52)
at 
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:160)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:124)
at 
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at 
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:127)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
at 
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1050)
at 
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1086)
at 
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at 
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
at 
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:66)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:127)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
at 
com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at 
com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1050)
at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
at 
org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
at 
org.eclipse.sisu.plexus.PlexusRequirements$RequirementProvider.get(PlexusRequirements.java:250)
at 
org.eclipse.sisu.plexus.ProvidedPropertyBinding.injectProperty(ProvidedPropertyBinding.java:48)
at 
org.eclipse.sisu.bean.BeanInjector.injectMembers(BeanInjector.java:52)
at 
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:160)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:124)
at 
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at 
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:127)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
at 
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
at 
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
at