[GitHub] maven-surefire issue #157: SUREFIRE-1383 dependenciesToScan Does Not Leverag...

2017-07-25 Thread owenfarrell
Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
And I got busy with other work as well. I think I found a solution that 
doesn't completely violate the pattern used by integration tests.

Long story short, the IT for SUREFIRE-569 has been updated to be completely 
independent modules. The first module leverages the flatten plugin to avoid any 
parent references, which then allows the second module to complete successfully.

The IT for SUREFIRE-1383 executes within a single process and verifies the 
updates that I've proposed.

Sorry for all the noise on the ticket - I hosed my fork while making the 
last round of updates.


---
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-surefire pull request #157: SUREFIRE-1383 dependenciesToScan Does Not ...

2017-07-25 Thread owenfarrell
GitHub user owenfarrell reopened a pull request:

https://github.com/apache/maven-surefire/pull/157

SUREFIRE-1383 dependenciesToScan Does Not Leverage Classpath Elements

Added logic to prefer output directories of projects built as part of the 
current session.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/owenfarrell/maven-surefire master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-surefire/pull/157.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #157


commit ee3b5be037c70d2a4667d786d4c487cf89ebfdfa
Author: Owen Farrell 
Date:   2017-07-26T02:30:52Z

SUREFIRE-1383: Added logic to use build output directories for session 
projects in favor of installed artifacts




---
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-surefire issue #157: SUREFIRE-1383 dependenciesToScan Does Not Leverag...

2017-07-25 Thread Tibor17
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
I have been busy with other ticket. Where did we finish. Do you need a help?


---
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-surefire pull request #157: SUREFIRE-1383 dependenciesToScan Does Not ...

2017-07-25 Thread owenfarrell
Github user owenfarrell closed the pull request at:

https://github.com/apache/maven-surefire/pull/157


---
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] Apache Maven Compiler 3.6.2

2017-07-25 Thread Olivier Lamy
Hi,
I'd like to release Apache Maven Compiler Plugin version 3.6.2.

We fixed 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12339154

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

Source release:
*
https://repository.apache.org/content/repositories/maven-1348/org/apache/maven/plugins/maven-compiler-plugin/3.6.2/maven-compiler-plugin-3.6.2-source-release.zip

Staging site:
http://maven.apache.org/components/plugins-archives/maven-compiler-plugin-LATEST/
Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

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

My +1

Cheers

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


[GitHub] maven-indexer pull request #18: Sb 869 merge with apache master

2017-07-25 Thread fuss86
Github user fuss86 closed the pull request at:

https://github.com/apache/maven-indexer/pull/18


---
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-indexer pull request #18: Sb 869 merge with apache master

2017-07-25 Thread fuss86
GitHub user fuss86 opened a pull request:

https://github.com/apache/maven-indexer/pull/18

Sb 869 merge with apache master



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/carlspring/maven-indexer SB-869

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-indexer/pull/18.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #18


commit 4e9229c00cc58dcbfcc8bf8776d634e9200e5762
Author: Martin Todorov 
Date:   2015-04-29T14:17:44Z

Merge pull request #1 from apache/master

Merge from origin.

commit b87afd410092e30309b0cb2e66ff695541cd7bbb
Author: Przemyslaw Fusik 
Date:   2017-04-23T11:14:44Z

Merge branch 'master' of https://github.com/apache/maven-indexer into SB-788

commit b525b6338d7d5f98dca722590413fbca6e1cc12a
Author: Martin Todorov 
Date:   2017-04-23T17:40:48Z

Merge pull request #2 from fuss86/SB-788

SB-788 strongbox forked master merged with latest apache master

commit 14b0418a6c07ac021a68b450177e16a83af12655
Author: Przemyslaw Fusik 
Date:   2017-07-25T21:33:30Z

Merge branch 'master' of https://github.com/apache/maven-indexer




---
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



How to exclude xml junit report in Jenkinsfile?

2017-07-25 Thread Tibor Digana
How to exclude *.xml in junit report in Jenkinsfile?

I used ! like this :

junit allowEmptyResults: true,
testResults:'**/target/failsafe-reports/*.xml,!**/combined-auditmodule-cdi-extension/**/*.xml,!**/duplicate-auditmodule-cdi-extension/**/*.xml,!**/duplicate-audituser-cdi-extension/**/*.xml,!**/ejb-async-audituser/**/*.xml,!**/suppressed-exception-no-void-return/**/*.xml'

But these 5 are still included.


-- 
Cheers
Tibor


[GitHub] maven-surefire issue #160: SUREFIRE-1398 Sets threadCount only when parallel...

2017-07-25 Thread Tibor17
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/160
  
If you plan a new commit, pls do not create two. Amend the previous one.
Thx.

On Tue, Jul 25, 2017 at 5:29 PM, Tibor Digana 
wrote:

> Pls check it together with documentation of param "forkMode". I think
> threadCount can be used with forkMode as well.
>
> On Tue, Jul 25, 2017 at 4:24 PM, Matous Jobanek 
> wrote:
>
>> Otherwise, the TestNG fails with
>> Cannot use a threadCount parameter less than 1; 1 > 0
>> in some cases when the parallel parameter was not set. To identify the
>> cases, take a look at related Jira issue: https://issues.apache.org/jira
>> /browse/SUREFIRE-1398
>> I removed the check for positiveness of the threadCount value as it's a
>> responsibility of the user to provide correct value.
>> The question is if the default value of threadCount parameter shouldn't
>> be 1, to avoid such a problems...? If yes, then I'll update my PR
>> --
>> You can view, comment on, or merge this pull request online at:
>>
>>   https://github.com/apache/maven-surefire/pull/160
>> Commit Summary
>>
>>- SUREFIRE-1398 Sets threadCount only when parallel parameter is set
>>
>> File Changes
>>
>>- *M* maven-surefire-common/src/main/java/org/apache/maven/plugin/
>>surefire/AbstractSurefireMojo.java
>> (13)
>>
>> Patch Links:
>>
>>- https://github.com/apache/maven-surefire/pull/160.patch
>>- https://github.com/apache/maven-surefire/pull/160.diff
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub
>> , or mute the thread
>> 

>> .
>>
>
>
>
> --
> Cheers
> Tibor
>



-- 
Cheers
Tibor



---
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-surefire issue #160: SUREFIRE-1398 Sets threadCount only when parallel...

2017-07-25 Thread Tibor17
Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/160
  
Pls check it together with documentation of param "forkMode". I think
threadCount can be used with forkMode as well.

On Tue, Jul 25, 2017 at 4:24 PM, Matous Jobanek 
wrote:

> Otherwise, the TestNG fails with
> Cannot use a threadCount parameter less than 1; 1 > 0
> in some cases when the parallel parameter was not set. To identify the
> cases, take a look at related Jira issue: https://issues.apache.org/
> jira/browse/SUREFIRE-1398
> I removed the check for positiveness of the threadCount value as it's a
> responsibility of the user to provide correct value.
> The question is if the default value of threadCount parameter shouldn't
> be 1, to avoid such a problems...? If yes, then I'll update my PR
> --
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/maven-surefire/pull/160
> Commit Summary
>
>- SUREFIRE-1398 Sets threadCount only when parallel parameter is set
>
> File Changes
>
>- *M* maven-surefire-common/src/main/java/org/apache/maven/
>plugin/surefire/AbstractSurefireMojo.java
> (13)
>
> Patch Links:
>
>- https://github.com/apache/maven-surefire/pull/160.patch
>- https://github.com/apache/maven-surefire/pull/160.diff
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> , or mute the thread
> 

> .
>



-- 
Cheers
Tibor



---
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-surefire pull request #160: SUREFIRE-1398 Sets threadCount only when p...

2017-07-25 Thread MatousJobanek
GitHub user MatousJobanek opened a pull request:

https://github.com/apache/maven-surefire/pull/160

SUREFIRE-1398 Sets threadCount only when parallel parameter is set

Otherwise, the TestNG fails with 
`Cannot use a threadCount parameter less than 1; 1 > 0` 
in some cases when the parallel parameter was not set. To identify the 
cases, take a look at related Jira issue: 
https://issues.apache.org/jira/browse/SUREFIRE-1398
I removed the check for positiveness of the `threadCount` value as it's a 
responsibility of the user to provide correct value.
The question is if the default value of `threadCount` parameter shouldn't 
be 1, to avoid such a problems...? If yes, then I'll update my PR

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MatousJobanek/maven-surefire SUREFIRE-1398

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-surefire/pull/160.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #160


commit 30df0c3fb5cc1f22caf0a9031155cb2d778b3fab
Author: Matous Jobanek 
Date:   2017-07-25T14:19:01Z

SUREFIRE-1398 Sets threadCount only when parallel parameter is set




---
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