Hi Igor,
looks like you hit the bull's eye...
thanks.
On 9/24/15 10:21 PM, Igor Fedorenko wrote:
Not sure if this answers your question, but MNG-5742 explains why you
see multiple @Singleton instances in maven 3.1.1 but not in 3.3.1. There
was related smaller MNG-5793 which I fixed in 3.3.3.
h
Not sure if this answers your question, but MNG-5742 explains why you
see multiple @Singleton instances in maven 3.1.1 but not in 3.3.1. There
was related smaller MNG-5793 which I fixed in 3.3.3.
https://issues.apache.org/jira/browse/MNG-5742
https://issues.apache.org/jira/browse/MNG-5793
--
Reg
Hi,
while i'm experimenting with LifeCycleParticipant i stumbled over a
thing which looks like a bug for me or a regression...or i misunderstand
a thing...
So the LifeCycle Participant is defined like this:
..
import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singl
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/105#issuecomment-142905726
@juherr I have to wait for #98 anyway which is critical bug and the guys in
Maven expect the fix. So we may take this commit as it is, that's fine, and
prove it
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/105#issuecomment-142898887
@juherr
That's pity. I will postpone the release in a week. Maybe I could help you
to write the IT in multiple commits.
---
If your project is set up for i
Github user juherr commented on the pull request:
https://github.com/apache/maven-surefire/pull/105#issuecomment-142852570
Thank! I will have a look but I'm not sure to succeed to propose something
before end of the month.
At least, it should be available for the EOY release.
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/2#issuecomment-142837160
Enabled by default would mean to introduce a new feature and new bugs and
requirements in Jira.
The reason why we want the users to implement the API in thei
