Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 1:23 PM, Andreas Gudian
 wrote:
> Benson, is there a full stack trace in the XML test report? I would have
> expected that we shorten out most of the stack traces on the console
> output...

No. That's why I complained.


>
> 2015-10-16 16:35 GMT+02:00 Benson Margulies :
>
>> On Fri, Oct 16, 2015 at 10:31 AM, Tibor Digana 
>> wrote:
>> > Can you give me the link?
>>
>>
>> https://github.com/ops4j/org.ops4j.pax.exam2/commit/c466e58cae6c2275a38bc2712cc76a70f768d769
>>
>>
>> >
>> > On Fri, Oct 16, 2015 at 4:27 PM, Benson Margulies [via Maven] <
>> > ml-node+s40175n5849346...@n5.nabble.com> wrote:
>> >
>> >> I've committed the fix to the master for pax-exam.
>> >>
>> >>
>> >> On Fri, Oct 16, 2015 at 10:19 AM, Benson Margulies
>> >> <[hidden email] > /user/SendEmail.jtp?type=node=5849346=0>>
>> >> wrote:
>> >>
>> >> > On Fri, Oct 16, 2015 at 9:56 AM, Tibor Digana
>> >> > <[hidden email] > /user/SendEmail.jtp?type=node=5849346=1>>
>> >> wrote:
>> >> >> try to debug this stack part of ProbeRunner.
>> >> >> What version of pax-exam-spi you use?
>> >> >
>> >> > 4.6.0. I am testing the fix to pax-exam now.
>> >> >
>> >> >>
>> >> >>  at org.ops4j.pax.exam.spi.
>> >> >>
>> >>
>> reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>> >> >>  at
>> >> >>
>> >>
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>> >>
>> >> >>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>> >> >>  at
>> >> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>> >> >>
>> >> >>
>> >> >> On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies <[hidden email]
>> >> >
>> >> >> wrote:
>> >> >>
>> >> >>> Step 1: here's the backtrace of the InvocationTargetException. It's
>> >> >>> caused by an IllegalArgumentException, which I will break on next.
>> >> >>>
>> >> >>> That is in turn, as you supposed, caused by the use of the file:
>> >> >>>
>> >> >>>
>> >> >>>
>> >>
>> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
>> >>
>> >> >>>
>> >> >>> being non-hierarchical.
>> >> >>>
>> >> >>> So, the underlying issue is a bug in pax-exam. However, I still
>> wonder
>> >> >>> what you think about the fact that failsafe did not provide any
>> >> >>> backtrace.
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> "main@1" prio=5 tid=0x1 nid=NA runnable
>> >> >>>   java.lang.Thread.State: RUNNABLE
>> >> >>>  at
>> >> >>>
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >>
>> >> >>>  at java.lang.reflect.Method.invoke(Method.java:497)
>> >> >>>  at
>> >> >>>
>> >>
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>> >>
>> >> >>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>> >> >>>  at
>> >> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>> >> >>>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
>> >> >>>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
>> >> >>>  at
>> >> >>>
>> >>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> >>
>> >> >>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>> >> >>>  at
>> >> >>>
>> >>
>> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>> >>
>> >> >>>  at
>> >> >>>
>> >>
>> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>> >>
>> >> >>>  at org.junit.runner.Computer.getRunner(Computer.java:40)
>> >> >>>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
>> >> >>>  at
>> >> >>>
>> >>
>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>> >>
>> >> >>>  at
>> >> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
>> >> >>>  at
>> >>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Andreas Gudian 
Benson, is there a full stack trace in the XML test report? I would have
expected that we shorten out most of the stack traces on the console
output...

2015-10-16 16:35 GMT+02:00 Benson Margulies :

> On Fri, Oct 16, 2015 at 10:31 AM, Tibor Digana 
> wrote:
> > Can you give me the link?
>
>
> https://github.com/ops4j/org.ops4j.pax.exam2/commit/c466e58cae6c2275a38bc2712cc76a70f768d769
>
>
> >
> > On Fri, Oct 16, 2015 at 4:27 PM, Benson Margulies [via Maven] <
> > ml-node+s40175n5849346...@n5.nabble.com> wrote:
> >
> >> I've committed the fix to the master for pax-exam.
> >>
> >>
> >> On Fri, Oct 16, 2015 at 10:19 AM, Benson Margulies
> >> <[hidden email]  /user/SendEmail.jtp?type=node=5849346=0>>
> >> wrote:
> >>
> >> > On Fri, Oct 16, 2015 at 9:56 AM, Tibor Digana
> >> > <[hidden email]  /user/SendEmail.jtp?type=node=5849346=1>>
> >> wrote:
> >> >> try to debug this stack part of ProbeRunner.
> >> >> What version of pax-exam-spi you use?
> >> >
> >> > 4.6.0. I am testing the fix to pax-exam now.
> >> >
> >> >>
> >> >>  at org.ops4j.pax.exam.spi.
> >> >>
> >>
> reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
> >> >>  at
> >> >>
> >>
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
> >>
> >> >>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
> >> >>  at
> >> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
> >> >>
> >> >>
> >> >> On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies <[hidden email]
> >> >
> >> >> wrote:
> >> >>
> >> >>> Step 1: here's the backtrace of the InvocationTargetException. It's
> >> >>> caused by an IllegalArgumentException, which I will break on next.
> >> >>>
> >> >>> That is in turn, as you supposed, caused by the use of the file:
> >> >>>
> >> >>>
> >> >>>
> >>
> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
> >>
> >> >>>
> >> >>> being non-hierarchical.
> >> >>>
> >> >>> So, the underlying issue is a bug in pax-exam. However, I still
> wonder
> >> >>> what you think about the fact that failsafe did not provide any
> >> >>> backtrace.
> >> >>>
> >> >>>
> >> >>>
> >> >>> "main@1" prio=5 tid=0x1 nid=NA runnable
> >> >>>   java.lang.Thread.State: RUNNABLE
> >> >>>  at
> >> >>>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
> >>
> >> >>>  at
> >> >>>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >>
> >> >>>  at
> >> >>>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>
> >> >>>  at java.lang.reflect.Method.invoke(Method.java:497)
> >> >>>  at
> >> >>>
> >>
> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
> >>
> >> >>>  at
> >> >>>
> >>
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
> >>
> >> >>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
> >> >>>  at
> >> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
> >> >>>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
> >> >>>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
> >> >>>  at
> >> >>>
> >>
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
> >>
> >> >>>  at
> >> >>>
> >>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> >>
> >> >>>  at
> >> >>>
> >>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> >>
> >> >>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> >> >>>  at
> >> >>>
> >>
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
> >>
> >> >>>  at
> >> >>>
> >>
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
> >>
> >> >>>  at
> >> >>>
> >>
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> >>
> >> >>>  at
> >> >>>
> >>
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
> >>
> >> >>>  at org.junit.runner.Computer.getRunner(Computer.java:40)
> >> >>>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
> >> >>>  at
> >> >>>
> >>
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> >>
> >> >>>  at
> >> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
> >> >>>  at
> >> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
> >> >>>  at org.junit.runners.Suite.(Suite.java:81)
> >> >>>  at org.junit.runner.Computer.getSuite(Computer.java:28)
> >> >>>  at org.junit.runner.Request.classes(Request.java:75)
> >> >>>  at

Re: [VOTE] Release Apache Maven Release version 2.5.3

2015-10-16 Thread Karl Heinz Marbaise 

Hi,

here we need one more binding VOTE...
Kind regards
Karl Heinz Marbaise
On 10/14/15 6:05 PM, Karl Heinz Marbaise wrote:

Hi Benson,

shasum checked Ok.

checked via mvn -Prun-its clean verify

Maven 3.0.5, 3.1.1, 3.2.5, 3.3.3 without any issue...

so +1 from me...

Kind regards
Karl Heinz Marbaise


On 10/14/15 2:05 PM, Benson Margulies wrote:

Hi,

We solved 2 issues:

Release Notes - Maven Release Plugin - Version 2.5.3

** Bug
 * [MRELEASE-921] - perform goal doesn't support
providerImplementation
 * [MRELEASE-925] - Old version of plexus utils forced here causes
failures


There are still a couple of issues left in JIRA:

https://issues.apache.org/jira/browse/MRELEASE-726?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1219

https://repository.apache.org/service/local/repositories/maven-1219/content/org/apache/maven/release/maven-release/2.5.3/maven-release-2.5.3-source-release.zip


Source release checksum(s):
[NAME-OF]-source-release.zip sha1:
2e8f11f48b4a4196c9ea06b8569f55ae68805506]

Staging site:
http://maven.apache.org/maven-release-archives/maven-release-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

My +1.


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

Failing IT's ([MNG-5898]) Jenkins

2015-10-16 Thread Karl Heinz Marbaise 

Hi,

currently i'm trying to fix an issue [MNG-5898]...

and currently having a single IT which fails..

mng5214DontMapWsdlToJar

So don't be scared about the failing IT's i'm working on that...


Kind regards
Karl Heinz Marbaise

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

[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2015-10-16 Thread barthel 
Github user barthel commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-148653328
  
@michael-o There is a typo and not a hidden statement. :-D


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2015-10-16 Thread michael-o 
Github user michael-o commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-148634870
  
@ChristianSchulte Maybe `Rage` is intentional ;-)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] maven-plugins pull request: Updated docs URL for shade plugin

2015-10-16 Thread edwardmlyte 
Github user edwardmlyte closed the pull request at:

https://github.com/apache/maven-plugins/pull/59


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: VOTE] Release Apache Maven Shared Archiver 3.0.0

2015-10-16 Thread Karl Heinz Marbaise 

Hi,

here is my +1..

Kind regards
Karl Heinz Marbaise

On 10/14/15 8:51 PM, Karl Heinz Marbaise wrote:

Hi,

Note: This is a Maven 3.0 / JDK 6 release

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12333673


There are several issue open:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1220/
https://repository.apache.org/content/repositories/maven-1220/org/apache/maven/maven-archiver/3.0.0/maven-archiver-3.0.0-source-release.zip


Source release checksum(s):
maven-archiver-3.0.0-source-release.zip sha1:
2c03268faa0c72eb24b1f2657ce96e26aaa2f6f1

Staging site:
http://maven.apache.org/shared-archives/maven-archiver-LATEST/


Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


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

[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2015-10-16 Thread barthel 
Github user barthel commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-148659197
  
@michael-o Your comment on 'old' commit 
b6d72699c8b0089351f797e217d635424c1ae5a2:
> Don't! Always through a NPE if null is passed.

:+1: But, I'm oriented on the current used pattern like in 
#setRepositoryEventDispatcher or #setSyncContextFactory.

> Right, see my ongoing effort on this: 
https://issues.apache.org/jira/browse/MNG-5649

Should I adapt the other methods? It's not the original intention of this 
PR.
Maybe I create a branch and/or new commit with these changes only.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: [VOTE] Release Maven Checkstyle Plugin version 2.17

2015-10-16 Thread Karl Heinz Marbaise 

Hi,

shasum Checked Ok.

Checked via mvn -Prun-its clean verify

with: Maven 3.0.5, 3.1.1, 3.2.5, 3.3.3

without any issue..

So +1 from me

Kind regards
Karl Heinz Marbaise
On 10/15/15 8:59 PM, Michael Osipov wrote:

Hi,

We solved 7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223=12333072


There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project+%3D+MCHECKSTYLE+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC


Staging repo:
https://repository.apache.org/content/repositories/maven-1223/
https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17-source-release.zip


Source release checksum(s):
maven-checkstyle-plugin-2.17-source-release.zip sha1:
73c72f082ec3ee2a89f54563f8d65393cd6f3886

Staging site:
http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


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

[GitHub] maven-plugins pull request: Prevents NPE in getMismatch

2015-10-16 Thread o-orand 
Github user o-orand closed the pull request at:

https://github.com/apache/maven-plugins/pull/62


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[VOTE] Release Apache Maven Shade Plugin version 2.4.2

2015-10-16 Thread Karl Heinz Marbaise 

Hi,

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12333008

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1224
https://repository.apache.org/content/repositories/maven-1224/org/apache/maven/plugins/maven-shade-plugin/2.4.2/maven-shade-plugin-2.4.2-source-release.zip

Source release checksum(s):
maven-shade-plugin-2.4.2-source-release.zip sha1: 
a42917c7e6cfa08e122afdd209dc9b8394de2d42


Staging site:
http://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/


Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Karl Heinz Marbaise

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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Tibor Digana 
We need two more voters of +1.
We are in the middle of the Vote.

On Thu, Oct 15, 2015 at 3:48 AM, Tibor Digana 
wrote:

> Hi,
>
> We solved 57 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12331679
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1222
>
> https://repository.apache.org/service/local/repositories/maven-1222/content/org/apache/maven/surefire/surefire/2.19/surefire-2.19-source-release.zip
>
> Source release checksum(s):
> surefire-2.19-source-release.zip sha1:
> db2592184236939f7d09f523a389c5241159d3ca
>
> Staging site:
> http://maven.apache.org/surefire-archives/surefire-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>

Problem testing the checkstyle release

2015-10-16 Thread Benson Margulies 
Maven-plugins 28 is released, of course; what's up? It worked for me,
but not for one of my co-workers.

$ mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building Parent for Text Analytics Maven Projects 57.2.4-SNAPSHOT
[INFO] 
Downloading: 
https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
Downloaded: 
https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
(14 KB at 7.7 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
Downloading: 
http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
Downloading: 
http://nexus.basistech.net:8081/nexus/content/groups/public/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
[INFO] 
[INFO] BUILD FAILURE

[ERROR] Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17
or one of its dependencies could not be resolved: Failed to read
artifact descriptor for
org.apache.maven.plugins:maven-checkstyle-plugin:jar:2.17: Could not
find artifact org.apache.maven.plugins:maven-plugins:pom:28 in
checkstyle-stage
(https://repository.apache.org/content/repositories/maven-1223/) ->
[Help 1]

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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 8:20 AM, Tibor Digana  wrote:
> https://repository.apache.org/content/repositories/maven-1222

Tested on my current major project. No issues. +1 binding.

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

Re: [VOTE] Release Maven Checkstyle Plugin version 2.17

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 5:53 AM, Karl Heinz Marbaise  wrote:
> http://maven.apache.org/guides/development/guide-testing-releases.html



+1

Ran it on one of my projects, where it promptly exploded due to
checkstyle incompatibilities. So I know it worked.

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

[GitHub] maven pull request: MNG-3092: Adds version range result filter beh...

2015-10-16 Thread barthel 
Github user barthel commented on the pull request:

https://github.com/apache/maven/pull/70#issuecomment-148704373
  
@ChristianSchulte Typo fixed. Thanks for looking into it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Re: Problem testing the checkstyle release

2015-10-16 Thread Anders Hammar 
No, you don't. Maybe there is some cached metadata incorrect or the
metadata at apache.
Could you try adding the -U switch?

Also, I only have the staging repo in my settings as a profile and I only
activate it explicitly when testing staged stuff.

/Anders (mobile)
Den 16 okt 2015 15:35 skrev "Benson Margulies" :

> Anders, I added a pluginRepository for the stage to my settings.xml.
> As far as I know,  adds, it
> doesn't replace.
>
> So why isn't it searching for the parent in the usual way in the other
> repositories? Or do I have to manually put central in as a
> pluginRepository if I'm just trying to add one?
>
>
> On Fri, Oct 16, 2015 at 9:19 AM, Anders Hammar  wrote:
> > It looks like a specific staging repo is accessed (look at the URL in the
> > end). As the parent has been released it is no longer available there.
> >
> > /Anders (mobile)
> > Den 16 okt 2015 15:01 skrev "Benson Margulies" :
> >
> >> Maven-plugins 28 is released, of course; what's up? It worked for me,
> >> but not for one of my co-workers.
> >>
> >> $ mvn clean install
> >> [INFO] Scanning for projects...
> >> [INFO]
> >> [INFO]
> >> 
> >> [INFO] Building Parent for Text Analytics Maven Projects 57.2.4-SNAPSHOT
> >> [INFO]
> >> 
> >> Downloading:
> >>
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
> >> Downloaded:
> >>
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
> >> (14 KB at 7.7 KB/sec)
> >> Downloading:
> >>
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
> >> Downloading:
> >>
> http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
> >> Downloading:
> >>
> http://nexus.basistech.net:8081/nexus/content/groups/public/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
> >> [INFO]
> >> 
> >> [INFO] BUILD FAILURE
> >>
> >> [ERROR] Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17
> >> or one of its dependencies could not be resolved: Failed to read
> >> artifact descriptor for
> >> org.apache.maven.plugins:maven-checkstyle-plugin:jar:2.17: Could not
> >> find artifact org.apache.maven.plugins:maven-plugins:pom:28 in
> >> checkstyle-stage
> >> (https://repository.apache.org/content/repositories/maven-1223/) ->
> >> [Help 1]
> >>
> >> -
> >> 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
>
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
Step 1: here's the backtrace of the InvocationTargetException. It's
caused by an IllegalArgumentException, which I will break on next.

That is in turn, as you supposed, caused by the use of the file:

jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties

being non-hierarchical.

So, the underlying issue is a bug in pax-exam. However, I still wonder
what you think about the fact that failsafe did not provide any
backtrace.



"main@1" prio=5 tid=0x1 nid=NA runnable
  java.lang.Thread.State: RUNNABLE
 at 
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:497)
 at 
org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
 at 
org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
 - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
 at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
 at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
 at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
 at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
 at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
 at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
 at 
org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
 at 
org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
 at 
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
 at 
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
 at org.junit.runner.Computer.getRunner(Computer.java:40)
 at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
 at 
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
 at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
 at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
 at org.junit.runners.Suite.(Suite.java:81)
 at org.junit.runner.Computer.getSuite(Computer.java:28)
 at org.junit.runner.Request.classes(Request.java:75)
 at org.junit.runner.Request.classes(Request.java:91)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:497)
 at 
org.apache.maven.surefire.common.junit4.JUnit4Reflector.createRequest(JUnit4Reflector.java:67)
 at 
org.apache.maven.surefire.common.junit4.JUnit4ProviderUtil.createSuiteDescription(JUnit4ProviderUtil.java:111)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.createTestsDescription(JUnit4Provider.java:328)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:166)
 at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
 at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
 at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
Um, maybe I voted too soon. Using the new failsafe plugin, I get the
following, and no backtrace, on each of my integration test classes.
Any suggestions, Tibor?


---
Test set: com.basistech.ws.itest.FrontEndIT
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008
sec <<< FAILURE! - in com.basistech.ws.itest.FrontEndIT
initializationError(com.basistech.ws.itest.FrontEndIT)  Time elapsed:
0.004 sec  <<< ERROR!
org.ops4j.pax.exam.TestContainerException:
java.lang.reflect.InvocationTargetException
at 
com.basistech.ws.itest.FrontEndIT.paxConfiguration(FrontEndIT.java:44)

Effective pom:

 
maven-failsafe-plugin
2.19

  
integration-tests

  integration-test
  verify


  
true

/Users/benson/x/rosapi1.5/itests/tests/target
1.5.0-SNAPSHOT
/Users/benson/x/rosapi1.5/itests/tests
4.0.2
false
  
  

org.apache.karaf:org.apache.karaf.client

org.jboss.logging:jboss-logging

org.ops4j.pax.logging:pax-logging-service

org.ops4j.pax.logging:pax-logging-api
  

  


  
true
  
  

org.apache.karaf:org.apache.karaf.client

org.jboss.logging:jboss-logging

org.ops4j.pax.logging:pax-logging-service

org.ops4j.pax.logging:pax-logging-api
  

   wrote:
> On Fri, Oct 16, 2015 at 8:20 AM, Tibor Digana  wrote:
>> https://repository.apache.org/content/repositories/maven-1222
>
> Tested on my current major project. No issues. +1 binding.

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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Tibor Digana 
No idea what com.basistech.ws.itest.
FrontEndIT.paxConfiguration(FrontEndIT.java:44)
is doing, obviously some Java Reflection calls.

But don't expect that everything goes well because you maybe relied on one
of the bugs reported in Surefire.
Since now the failsafe plugin takes jar (built src/main/java) instead of
target/classes/.
If you rely on target/classes/, use surefire-plugin because that's what the
unit tests do.


On Fri, Oct 16, 2015 at 3:04 PM, Benson Margulies 
wrote:

> Um, maybe I voted too soon. Using the new failsafe plugin, I get the
> following, and no backtrace, on each of my integration test classes.
> Any suggestions, Tibor?
>
>
>
> ---
> Test set: com.basistech.ws.itest.FrontEndIT
>
> ---
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008
> sec <<< FAILURE! - in com.basistech.ws.itest.FrontEndIT
> initializationError(com.basistech.ws.itest.FrontEndIT)  Time elapsed:
> 0.004 sec  <<< ERROR!
> org.ops4j.pax.exam.TestContainerException:
> java.lang.reflect.InvocationTargetException
> at
> com.basistech.ws.itest.FrontEndIT.paxConfiguration(FrontEndIT.java:44)
>
> Effective pom:
>
>  
> maven-failsafe-plugin
> 2.19
> 
>   
> integration-tests
> 
>   integration-test
>   verify
> 
> 
>   
> true
>
>
> /Users/benson/x/rosapi1.5/itests/tests/target
> 1.5.0-SNAPSHOT
> /Users/benson/x/rosapi1.5/itests/tests
> 4.0.2
> false
>   
>   
>
>
> org.apache.karaf:org.apache.karaf.client
>
>
> org.jboss.logging:jboss-logging
>
>
> org.ops4j.pax.logging:pax-logging-service
>
>
> org.ops4j.pax.logging:pax-logging-api
>   
> 
>   
> 
> 
>   
> true
>   
>   
>
> org.apache.karaf:org.apache.karaf.client
>
> org.jboss.logging:jboss-logging
>
> org.ops4j.pax.logging:pax-logging-service
>
> org.ops4j.pax.logging:pax-logging-api
>   
> 
>   
>
>
> On Fri, Oct 16, 2015 at 8:55 AM, Benson Margulies 
> wrote:
> > On Fri, Oct 16, 2015 at 8:20 AM, Tibor Digana 
> wrote:
> >> https://repository.apache.org/content/repositories/maven-1222
> >
> > Tested on my current major project. No issues. +1 binding.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Cheers
Tibor

Re: [VOTE] Release Maven Checkstyle Plugin version 2.17

2015-10-16 Thread Daniel Kulp 
+1

Tested with CXF.  I did get an strange class loader error at first as CXF tried 
to force the checkstyle plugin to use checkstyle 6.4.1 (due to a bug in 6.5.x) 
which is apparently too old, but once I removed that, it was fine.  (and it 
appears the bug in 6.5 has been fixed, yea!)

Dan



> On Oct 15, 2015, at 2:59 PM, Michael Osipov  wrote:
> 
> Hi,
> 
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223=12333072
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project+%3D+MCHECKSTYLE+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1223/
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17-source-release.zip
> 
> Source release checksum(s):
> maven-checkstyle-plugin-2.17-source-release.zip sha1: 
> 73c72f082ec3ee2a89f54563f8d65393cd6f3886
> 
> Staging site:
> http://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


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

Re: Problem testing the checkstyle release

2015-10-16 Thread Benson Margulies 
Anders, I added a pluginRepository for the stage to my settings.xml.
As far as I know,  adds, it
doesn't replace.

So why isn't it searching for the parent in the usual way in the other
repositories? Or do I have to manually put central in as a
pluginRepository if I'm just trying to add one?


On Fri, Oct 16, 2015 at 9:19 AM, Anders Hammar  wrote:
> It looks like a specific staging repo is accessed (look at the URL in the
> end). As the parent has been released it is no longer available there.
>
> /Anders (mobile)
> Den 16 okt 2015 15:01 skrev "Benson Margulies" :
>
>> Maven-plugins 28 is released, of course; what's up? It worked for me,
>> but not for one of my co-workers.
>>
>> $ mvn clean install
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO]
>> 
>> [INFO] Building Parent for Text Analytics Maven Projects 57.2.4-SNAPSHOT
>> [INFO]
>> 
>> Downloading:
>> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
>> Downloaded:
>> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
>> (14 KB at 7.7 KB/sec)
>> Downloading:
>> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
>> Downloading:
>> http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
>> Downloading:
>> http://nexus.basistech.net:8081/nexus/content/groups/public/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>>
>> [ERROR] Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17
>> or one of its dependencies could not be resolved: Failed to read
>> artifact descriptor for
>> org.apache.maven.plugins:maven-checkstyle-plugin:jar:2.17: Could not
>> find artifact org.apache.maven.plugins:maven-plugins:pom:28 in
>> checkstyle-stage
>> (https://repository.apache.org/content/repositories/maven-1223/) ->
>> [Help 1]
>>
>> -
>> 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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Tibor Digana 
try to debug this stack part of ProbeRunner.
What version of pax-exam-spi you use?

 at org.ops4j.pax.exam.spi.
reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
 at
org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
 - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
 at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)


On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies 
wrote:

> Step 1: here's the backtrace of the InvocationTargetException. It's
> caused by an IllegalArgumentException, which I will break on next.
>
> That is in turn, as you supposed, caused by the use of the file:
>
>
> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
>
> being non-hierarchical.
>
> So, the underlying issue is a bug in pax-exam. However, I still wonder
> what you think about the fact that failsafe did not provide any
> backtrace.
>
>
>
> "main@1" prio=5 tid=0x1 nid=NA runnable
>   java.lang.Thread.State: RUNNABLE
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:497)
>  at
> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>  at
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>  at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
>  at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
>  at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>  at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>  at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>  at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>  at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>  at org.junit.runner.Computer.getRunner(Computer.java:40)
>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
>  at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>  at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
>  at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
>  at org.junit.runners.Suite.(Suite.java:81)
>  at org.junit.runner.Computer.getSuite(Computer.java:28)
>  at org.junit.runner.Request.classes(Request.java:75)
>  at org.junit.runner.Request.classes(Request.java:91)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:497)
>  at
> org.apache.maven.surefire.common.junit4.JUnit4Reflector.createRequest(JUnit4Reflector.java:67)
>  at
> org.apache.maven.surefire.common.junit4.JUnit4ProviderUtil.createSuiteDescription(JUnit4ProviderUtil.java:111)
>  at
> org.apache.maven.surefire.junit4.JUnit4Provider.createTestsDescription(JUnit4Provider.java:328)
>  at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:166)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Cheers
Tibor

Re: Problem testing the checkstyle release

2015-10-16 Thread Anders Hammar 
It looks like a specific staging repo is accessed (look at the URL in the
end). As the parent has been released it is no longer available there.

/Anders (mobile)
Den 16 okt 2015 15:01 skrev "Benson Margulies" :

> Maven-plugins 28 is released, of course; what's up? It worked for me,
> but not for one of my co-workers.
>
> $ mvn clean install
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
> 
> [INFO] Building Parent for Text Analytics Maven Projects 57.2.4-SNAPSHOT
> [INFO]
> 
> Downloading:
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
> Downloaded:
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
> (14 KB at 7.7 KB/sec)
> Downloading:
> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
> Downloading:
> http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
> Downloading:
> http://nexus.basistech.net:8081/nexus/content/groups/public/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
> [INFO]
> 
> [INFO] BUILD FAILURE
>
> [ERROR] Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17
> or one of its dependencies could not be resolved: Failed to read
> artifact descriptor for
> org.apache.maven.plugins:maven-checkstyle-plugin:jar:2.17: Could not
> find artifact org.apache.maven.plugins:maven-plugins:pom:28 in
> checkstyle-stage
> (https://repository.apache.org/content/repositories/maven-1223/) ->
> [Help 1]
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 9:34 AM, Tibor Digana
 wrote:
> No idea what com.basistech.ws.itest.
> FrontEndIT.paxConfiguration(FrontEndIT.java:44)
> is doing, obviously some Java Reflection calls.

No, it is not. Unless it's buried in pax-exam.

And if it were, don't you 'owe' me a full backtrace? I will see if I
can get one in IntelliJ ... that might be suggestive about what's
going on.

@Configuration
public static Option[] paxConfiguration() {
return new Option[]{
composite(Utils.baseConfiguration(frontEndPort, null)),
// this is here in case we decide to set up a mock worker.
replaceConfigurationFile("etc/anvils/transport-rules.tsv",
new File("src/config/front-end-transport-rules.tsv")),
Utils.distributionOption("rosapi-assembly-front-end")
};
}


Well, pax-exam is complex, and I can't rule out anything in it.




>
> But don't expect that everything goes well because you maybe relied on one
> of the bugs reported in Surefire.
> Since now the failsafe plugin takes jar (built src/main/java) instead of
> target/classes/.
> If you rely on target/classes/, use surefire-plugin because that's what the
> unit tests do.
>
>
> On Fri, Oct 16, 2015 at 3:04 PM, Benson Margulies 
> wrote:
>
>> Um, maybe I voted too soon. Using the new failsafe plugin, I get the
>> following, and no backtrace, on each of my integration test classes.
>> Any suggestions, Tibor?
>>
>>
>>
>> ---
>> Test set: com.basistech.ws.itest.FrontEndIT
>>
>> ---
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008
>> sec <<< FAILURE! - in com.basistech.ws.itest.FrontEndIT
>> initializationError(com.basistech.ws.itest.FrontEndIT)  Time elapsed:
>> 0.004 sec  <<< ERROR!
>> org.ops4j.pax.exam.TestContainerException:
>> java.lang.reflect.InvocationTargetException
>> at
>> com.basistech.ws.itest.FrontEndIT.paxConfiguration(FrontEndIT.java:44)
>>
>> Effective pom:
>>
>>  
>> maven-failsafe-plugin
>> 2.19
>> 
>>   
>> integration-tests
>> 
>>   integration-test
>>   verify
>> 
>> 
>>   
>> true
>>
>>
>> /Users/benson/x/rosapi1.5/itests/tests/target
>> 1.5.0-SNAPSHOT
>> /Users/benson/x/rosapi1.5/itests/tests
>> 4.0.2
>> false
>>   
>>   
>>
>>
>> org.apache.karaf:org.apache.karaf.client
>>
>>
>> org.jboss.logging:jboss-logging
>>
>>
>> org.ops4j.pax.logging:pax-logging-service
>>
>>
>> org.ops4j.pax.logging:pax-logging-api
>>   
>> 
>>   
>> 
>> 
>>   
>> true
>>   
>>   
>>
>> org.apache.karaf:org.apache.karaf.client
>>
>> org.jboss.logging:jboss-logging
>>
>> org.ops4j.pax.logging:pax-logging-service
>>
>> org.ops4j.pax.logging:pax-logging-api
>>   
>> 
>>   >
>>
>>
>> On Fri, Oct 16, 2015 at 8:55 AM, Benson Margulies 
>> wrote:
>> > On Fri, Oct 16, 2015 at 8:20 AM, Tibor Digana 
>> wrote:
>> >> https://repository.apache.org/content/repositories/maven-1222
>> >
>> > Tested on my current major project. No issues. +1 binding.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
> --
> Cheers
> Tibor

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

Re: Problem testing the checkstyle release

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 9:38 AM, Anders Hammar  wrote:
> No, you don't. Maybe there is some cached metadata incorrect or the
> metadata at apache.
> Could you try adding the -U switch?
>
> Also, I only have the staging repo in my settings as a profile and I only
> activate it explicitly when testing staged stuff.

Me too. That's what my co-worker was trying to do.

>
> /Anders (mobile)
> Den 16 okt 2015 15:35 skrev "Benson Margulies" :
>
>> Anders, I added a pluginRepository for the stage to my settings.xml.
>> As far as I know,  adds, it
>> doesn't replace.
>>
>> So why isn't it searching for the parent in the usual way in the other
>> repositories? Or do I have to manually put central in as a
>> pluginRepository if I'm just trying to add one?
>>
>>
>> On Fri, Oct 16, 2015 at 9:19 AM, Anders Hammar  wrote:
>> > It looks like a specific staging repo is accessed (look at the URL in the
>> > end). As the parent has been released it is no longer available there.
>> >
>> > /Anders (mobile)
>> > Den 16 okt 2015 15:01 skrev "Benson Margulies" :
>> >
>> >> Maven-plugins 28 is released, of course; what's up? It worked for me,
>> >> but not for one of my co-workers.
>> >>
>> >> $ mvn clean install
>> >> [INFO] Scanning for projects...
>> >> [INFO]
>> >> [INFO]
>> >> 
>> >> [INFO] Building Parent for Text Analytics Maven Projects 57.2.4-SNAPSHOT
>> >> [INFO]
>> >> 
>> >> Downloading:
>> >>
>> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
>> >> Downloaded:
>> >>
>> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-checkstyle-plugin/2.17/maven-checkstyle-plugin-2.17.pom
>> >> (14 KB at 7.7 KB/sec)
>> >> Downloading:
>> >>
>> https://repository.apache.org/content/repositories/maven-1223/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
>> >> Downloading:
>> >>
>> http://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
>> >> Downloading:
>> >>
>> http://nexus.basistech.net:8081/nexus/content/groups/public/org/apache/maven/plugins/maven-plugins/28/maven-plugins-28.pom
>> >> [INFO]
>> >> 
>> >> [INFO] BUILD FAILURE
>> >>
>> >> [ERROR] Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.17
>> >> or one of its dependencies could not be resolved: Failed to read
>> >> artifact descriptor for
>> >> org.apache.maven.plugins:maven-checkstyle-plugin:jar:2.17: Could not
>> >> find artifact org.apache.maven.plugins:maven-plugins:pom:28 in
>> >> checkstyle-stage
>> >> (https://repository.apache.org/content/repositories/maven-1223/) ->
>> >> [Help 1]
>> >>
>> >> -
>> >> 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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 9:56 AM, Tibor Digana
 wrote:
> try to debug this stack part of ProbeRunner.
> What version of pax-exam-spi you use?

4.6.0. I am testing the fix to pax-exam now.

>
>  at org.ops4j.pax.exam.spi.
> reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>  at
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>  at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>
>
> On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies 
> wrote:
>
>> Step 1: here's the backtrace of the InvocationTargetException. It's
>> caused by an IllegalArgumentException, which I will break on next.
>>
>> That is in turn, as you supposed, caused by the use of the file:
>>
>>
>> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
>>
>> being non-hierarchical.
>>
>> So, the underlying issue is a bug in pax-exam. However, I still wonder
>> what you think about the fact that failsafe did not provide any
>> backtrace.
>>
>>
>>
>> "main@1" prio=5 tid=0x1 nid=NA runnable
>>   java.lang.Thread.State: RUNNABLE
>>  at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>>  at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  at java.lang.reflect.Method.invoke(Method.java:497)
>>  at
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>>  at
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>>  at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
>>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
>>  at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
>>  at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>  at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>>  at
>> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>>  at
>> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>>  at
>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>>  at
>> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>>  at org.junit.runner.Computer.getRunner(Computer.java:40)
>>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
>>  at
>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>>  at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
>>  at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
>>  at org.junit.runners.Suite.(Suite.java:81)
>>  at org.junit.runner.Computer.getSuite(Computer.java:28)
>>  at org.junit.runner.Request.classes(Request.java:75)
>>  at org.junit.runner.Request.classes(Request.java:91)
>>  at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>>  at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  at java.lang.reflect.Method.invoke(Method.java:497)
>>  at
>> org.apache.maven.surefire.common.junit4.JUnit4Reflector.createRequest(JUnit4Reflector.java:67)
>>  at
>> org.apache.maven.surefire.common.junit4.JUnit4ProviderUtil.createSuiteDescription(JUnit4ProviderUtil.java:111)
>>  at
>> org.apache.maven.surefire.junit4.JUnit4Provider.createTestsDescription(JUnit4Provider.java:328)
>>  at
>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:166)
>>  at
>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
>>  at
>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
>>  at
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>
>
> --
> Cheers
> Tibor

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

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
I've committed the fix to the master for pax-exam.


On Fri, Oct 16, 2015 at 10:19 AM, Benson Margulies
 wrote:
> On Fri, Oct 16, 2015 at 9:56 AM, Tibor Digana
>  wrote:
>> try to debug this stack part of ProbeRunner.
>> What version of pax-exam-spi you use?
>
> 4.6.0. I am testing the fix to pax-exam now.
>
>>
>>  at org.ops4j.pax.exam.spi.
>> reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>>  at
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>>  at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>>
>>
>> On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies 
>> wrote:
>>
>>> Step 1: here's the backtrace of the InvocationTargetException. It's
>>> caused by an IllegalArgumentException, which I will break on next.
>>>
>>> That is in turn, as you supposed, caused by the use of the file:
>>>
>>>
>>> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
>>>
>>> being non-hierarchical.
>>>
>>> So, the underlying issue is a bug in pax-exam. However, I still wonder
>>> what you think about the fact that failsafe did not provide any
>>> backtrace.
>>>
>>>
>>>
>>> "main@1" prio=5 tid=0x1 nid=NA runnable
>>>   java.lang.Thread.State: RUNNABLE
>>>  at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>>>  at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>  at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>  at java.lang.reflect.Method.invoke(Method.java:497)
>>>  at
>>> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>>>  at
>>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>>>  at org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>>>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
>>>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
>>>  at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
>>>  at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>>  at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>>>  at
>>> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>>>  at
>>> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>>>  at
>>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>>>  at
>>> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>>>  at org.junit.runner.Computer.getRunner(Computer.java:40)
>>>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
>>>  at
>>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>>>  at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
>>>  at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
>>>  at org.junit.runners.Suite.(Suite.java:81)
>>>  at org.junit.runner.Computer.getSuite(Computer.java:28)
>>>  at org.junit.runner.Request.classes(Request.java:75)
>>>  at org.junit.runner.Request.classes(Request.java:91)
>>>  at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>>>  at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>  at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>  at java.lang.reflect.Method.invoke(Method.java:497)
>>>  at
>>> org.apache.maven.surefire.common.junit4.JUnit4Reflector.createRequest(JUnit4Reflector.java:67)
>>>  at
>>> org.apache.maven.surefire.common.junit4.JUnit4ProviderUtil.createSuiteDescription(JUnit4ProviderUtil.java:111)
>>>  at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.createTestsDescription(JUnit4Provider.java:328)
>>>  at
>>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:166)
>>>  at
>>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
>>>  at
>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
>>>  at
>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Cheers
>> Tibor

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Tibor Digana 
Can you give me the link?

On Fri, Oct 16, 2015 at 4:27 PM, Benson Margulies [via Maven] <
ml-node+s40175n5849346...@n5.nabble.com> wrote:

> I've committed the fix to the master for pax-exam.
>
>
> On Fri, Oct 16, 2015 at 10:19 AM, Benson Margulies
> <[hidden email] >
> wrote:
>
> > On Fri, Oct 16, 2015 at 9:56 AM, Tibor Digana
> > <[hidden email] >
> wrote:
> >> try to debug this stack part of ProbeRunner.
> >> What version of pax-exam-spi you use?
> >
> > 4.6.0. I am testing the fix to pax-exam now.
> >
> >>
> >>  at org.ops4j.pax.exam.spi.
> >>
> reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
> >>  at
> >>
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>
> >>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
> >>  at
> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
> >>
> >>
> >> On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies <[hidden email]
> >
> >> wrote:
> >>
> >>> Step 1: here's the backtrace of the InvocationTargetException. It's
> >>> caused by an IllegalArgumentException, which I will break on next.
> >>>
> >>> That is in turn, as you supposed, caused by the use of the file:
> >>>
> >>>
> >>>
> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
>
> >>>
> >>> being non-hierarchical.
> >>>
> >>> So, the underlying issue is a bug in pax-exam. However, I still wonder
> >>> what you think about the fact that failsafe did not provide any
> >>> backtrace.
> >>>
> >>>
> >>>
> >>> "main@1" prio=5 tid=0x1 nid=NA runnable
> >>>   java.lang.Thread.State: RUNNABLE
> >>>  at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>
> >>>  at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> >>>  at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> >>>  at java.lang.reflect.Method.invoke(Method.java:497)
> >>>  at
> >>>
> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>
> >>>  at
> >>>
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>
> >>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
> >>>  at
> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
> >>>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
> >>>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
> >>>  at
> >>>
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
>
> >>>  at
> >>>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>
> >>>  at
> >>>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> >>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> >>>  at
> >>>
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>
> >>>  at
> >>>
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>
> >>>  at
> >>>
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>
> >>>  at
> >>>
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>
> >>>  at org.junit.runner.Computer.getRunner(Computer.java:40)
> >>>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
> >>>  at
> >>>
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>
> >>>  at
> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
> >>>  at
> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
> >>>  at org.junit.runners.Suite.(Suite.java:81)
> >>>  at org.junit.runner.Computer.getSuite(Computer.java:28)
> >>>  at org.junit.runner.Request.classes(Request.java:75)
> >>>  at org.junit.runner.Request.classes(Request.java:91)
> >>>  at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>
> >>>  at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> >>>  at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> >>>  at java.lang.reflect.Method.invoke(Method.java:497)
> >>>  at
> >>>
> org.apache.maven.surefire.common.junit4.JUnit4Reflector.createRequest(JUnit4Reflector.java:67)
>
> >>>  at
> >>>
> org.apache.maven.surefire.common.junit4.JUnit4ProviderUtil.createSuiteDescription(JUnit4ProviderUtil.java:111)
>
> >>>  at
> >>>
> org.apache.maven.surefire.junit4.JUnit4Provider.createTestsDescription(JUnit4Provider.java:328)
>
> >>>  at
> >>>
>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

2015-10-16 Thread Benson Margulies 
On Fri, Oct 16, 2015 at 10:31 AM, Tibor Digana  wrote:
> Can you give me the link?

https://github.com/ops4j/org.ops4j.pax.exam2/commit/c466e58cae6c2275a38bc2712cc76a70f768d769


>
> On Fri, Oct 16, 2015 at 4:27 PM, Benson Margulies [via Maven] <
> ml-node+s40175n5849346...@n5.nabble.com> wrote:
>
>> I've committed the fix to the master for pax-exam.
>>
>>
>> On Fri, Oct 16, 2015 at 10:19 AM, Benson Margulies
>> <[hidden email] >
>> wrote:
>>
>> > On Fri, Oct 16, 2015 at 9:56 AM, Tibor Digana
>> > <[hidden email] >
>> wrote:
>> >> try to debug this stack part of ProbeRunner.
>> >> What version of pax-exam-spi you use?
>> >
>> > 4.6.0. I am testing the fix to pax-exam now.
>> >
>> >>
>> >>  at org.ops4j.pax.exam.spi.
>> >>
>> reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>> >>  at
>> >>
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>>
>> >>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>> >>  at
>> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>> >>
>> >>
>> >> On Fri, Oct 16, 2015 at 3:46 PM, Benson Margulies <[hidden email]
>> >
>> >> wrote:
>> >>
>> >>> Step 1: here's the backtrace of the InvocationTargetException. It's
>> >>> caused by an IllegalArgumentException, which I will break on next.
>> >>>
>> >>> That is in turn, as you supposed, caused by the use of the file:
>> >>>
>> >>>
>> >>>
>> jar:file:/Users/benson/x/rosapi1.5/itests/tests/target/rosapi-itests-tests.jar!/META-INF/maven/dependencies.properties
>>
>> >>>
>> >>> being non-hierarchical.
>> >>>
>> >>> So, the underlying issue is a bug in pax-exam. However, I still wonder
>> >>> what you think about the fact that failsafe did not provide any
>> >>> backtrace.
>> >>>
>> >>>
>> >>>
>> >>> "main@1" prio=5 tid=0x1 nid=NA runnable
>> >>>   java.lang.Thread.State: RUNNABLE
>> >>>  at
>> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>>
>> >>>  at
>> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> >>>  at
>> >>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> >>>  at java.lang.reflect.Method.invoke(Method.java:497)
>> >>>  at
>> >>>
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:239)
>>
>> >>>  at
>> >>>
>> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
>>
>> >>>  - locked <0x411> (a org.ops4j.pax.exam.spi.reactors.ReactorManager)
>> >>>  at
>> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:78)
>> >>>  at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
>> >>>  at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
>> >>>  at
>> >>>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
>>
>> >>>  at
>> >>>
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>
>> >>>  at
>> >>>
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>
>> >>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>> >>>  at
>> >>>
>> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)
>>
>> >>>  at
>> >>>
>> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)
>>
>> >>>  at
>> >>>
>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>>
>> >>>  at
>> >>>
>> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>>
>> >>>  at org.junit.runner.Computer.getRunner(Computer.java:40)
>> >>>  at org.junit.runner.Computer$1.runnerForClass(Computer.java:31)
>> >>>  at
>> >>>
>> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>>
>> >>>  at
>> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101)
>> >>>  at
>> org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87)
>> >>>  at org.junit.runners.Suite.(Suite.java:81)
>> >>>  at org.junit.runner.Computer.getSuite(Computer.java:28)
>> >>>  at org.junit.runner.Request.classes(Request.java:75)
>> >>>  at org.junit.runner.Request.classes(Request.java:91)
>> >>>  at
>> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-1)
>>
>> >>>  at
>> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> >>>  at
>> >>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> >>>  at java.lang.reflect.Method.invoke(Method.java:497)
>> >>>  at
>> >>>
>> org.apache.maven.surefire.common.junit4.JUnit4Reflector.createRequest(JUnit4Reflector.java:67)
>>
>> >>>  at
>> >>>

Problems updating to Maven x >= 3.1.1

2015-10-16 Thread Christofer Dutz 
Hi,


I am currently trying to fix a problem with the newly open-sourced Flex plugin 
for IntelliJ.


In this plugin usually a goal of a maven plugin (Flexmojos) is executed 
programmatically in order to generate a config file, which IntelliJ then uses 
to configure itself. For this they manually construct a PlexusContainer and use 
that to do all sorts of magic.


The problem is that when updating Flexmojos 7.1.0-SNAPSHOT I had to make it 
depend on at least Maven 3.1.1 as some of the resource resolution stuff had 
changed there. Unfortunately If I use anything above 3.1.0 the IntelliJ plugin 
doesn't work and it gives me this Error:


[main] WARN Sisu - Error injecting: 
org.apache.maven.plugin.DefaultBuildPluginManager
com.google.inject.ProvisionException: Guice provision errors:

1) No implementation for 
org.apache.maven.execution.scope.internal.MojoExecutionScope was bound.
  while locating org.apache.maven.plugin.DefaultBuildPluginManager

I get this when looking up "Maven":

org.apache.maven.Maven maven = 
plexusContainer.lookup(org.apache.maven.Maven.class);

The method doing this actually wants to create a RepositorySystemSession ... so 
eventually there is a different way, than to get the maven instance and then 
call newRepositorySession on that.


I know that inside maven there actually is no longer a real classic plexus 
container running ... so eventually it would be better to use Guice instead. 
Any pointers towards how to programmatically get a RepositorySystemSession 
would be great ;-)


Chris