Am 2017-06-04 um 20:55 schrieb Karl Heinz Marbaise:
Hi,
I would like to suggest to introduce:
MNG-6206
MNG-6207
to be part of Maven 3.5.1...
Currently for MNG-6206 we have a pull request which solves the issue
also the IT's are Ok for this.
I will check also for MNG-6207..
If there are no o
Github user dejan2609 commented on the issue:
https://github.com/apache/maven/pull/121
@khmarbaise
Integration tests passed as expected, that's nice.
Commit message is altered just a little bit and force-pushed here.
---
If your project is set up for it, you ca
Github user dejan2609 commented on the issue:
https://github.com/apache/maven/pull/119
@khmarbaise done, I altered commit messaged (added note about tests).
---
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
Hi,
I would like to suggest to introduce:
MNG-6206
MNG-6207
to be part of Maven 3.5.1...
Currently for MNG-6206 we have a pull request which solves the issue
also the IT's are Ok for this.
I will check also for MNG-6207..
If there are no objections I will integrate them after the have been
Github user khmarbaise commented on the issue:
https://github.com/apache/maven/pull/119
Could you make a real commit log message like:
```
[MNG-6207] Create WARNINGs in case of using system scope
If needed more description/explanations here.
```
Otherwise I need to
Github user khmarbaise commented on the issue:
https://github.com/apache/maven/pull/121
Please make a complete commit message with reference to the appropriate
ticket.
```
[MNG-6206] display deprecation build warning in case when dependencies use
metaversions (LATEST or RELEAS
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/146
@mgreau
@britter
Hey guys, let's utilize your power and complete `AbstractSurefireMojo` with
`ProviderInfo`, some tests are still in progress.
Meanwhile Apache Maven will complet
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@britter
We have to finish 2.20.1 but we can finish the junit5 provider. Where did
we finish last time?
---
If your project is set up for it, you can reply to this email and have your
r
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/146
@Tibor17 the provider is already part of the 3.0-rc1 branch. Please see
#142. This just fixes an incorrect module name.
> It's not legal to introduce incomplete feature.
Sinc
Github user michael-o commented on the issue:
https://github.com/apache/maven-surefire/pull/141
2.20.1 will go first.
---
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
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@Tibor17 what about this?
---
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 an
So I have 27 releases of XStream unzipped and pushed to
https://github.com/paul-hammant/mc-xs-classes
(8.4M of Jars is now 2.4M of bare .git repo)
All the jars are still available - here -
https://github.com/paul-hammant/mc-xs-classes/releases
Perfect except:
1. .zip suffix instead of .jar
Am 2017-06-03 um 13:53 schrieb Tibor Digana:
Hi Michael,
I have pushed branch SUREFIRE-1380_2, see [1], and separated the previous
ticket SUREFIRE-1380 to two: SUREFIRE-1380 and SUREFIRE-1381.
The branch SUREFIRE-1380_2 is for Jira SUREFIRE-1380.
[1]:
https://git-wip-us.apache.org/repos/asf?p=m
13 matches
Mail list logo
