Am 10/13/16 um 21:52 schrieb Robert Scholte:
> On Thu, 13 Oct 2016 02:53:54 +0200, Christian Schulte
>> Should I change the order of the effective settings so that things from
>> the global settings always come before the user settings? Will that blow
>> up somewhere else. We
Am 10/13/16 um 21:52 schrieb Robert Scholte:
> I'd say revert these changes. We see that this "hack" doesn't always work.
> Better look for a more solid solution with another release in the future.
The better solution would be to completely remove repositories from the
poms and from all
Hello,
reverting seems safer. As settings always override stuff in poms, my guess
would be that having global defining stuff for central will blow stuff for
lots of people. Overriding central seems very natural. And user's settings
will survive updates of Maven it self.
Regards
Mirko
--
Sent
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/129
Thank you!
---
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,
On Thu, 13 Oct 2016 02:53:54 +0200, Christian Schulte
wrote:
Am 10/12/16 um 23:17 schrieb Robert Scholte:
It is a bit different: the *effective* settings are the global settings
where parts can be overridden with the user settings. This means that
all
profiles will be
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/129
done
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/129
---
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
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/122
We have such feature in Surefire. It is called "runorder". Makes sense
since the second run.
On Thu, Oct 13, 2016 at 9:04 AM, Denis Saponenko
wrote:
GitHub user britter opened a pull request:
https://github.com/apache/maven-surefire/pull/129
Merge master to junit5 branch
As discussed on the ML.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/britter/maven-surefire
Github user axel3rd closed the pull request at:
https://github.com/apache/maven-plugins/pull/95
---
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
Hi Hervé,
Tunaki propose to update the PR with an IT based on a push on local file
... more simple & sustainable, and will push it.
Many thanks to you.
Best regards.
2016-10-13 8:44 GMT+02:00 Hervé BOUTEMY :
> Hi Alix,
>
> Thanks for the patch: I'll review it this WE.
>
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/128
---
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
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/128
@Tibor17 I think I'll wait until this is reintegrated, before I make a PR
for merging master to junit5.
---
If your project is set up for it, you can reply to this email and have your
reply
same issue with maven-pmd-plugin-3.6: there's something strange on my
machine...
then +1
Regards,
Hervé
Le jeudi 13 octobre 2016 20:02:27 Andreas Dangel a écrit :
> That's weird. I don't see this... I'm on Linux, too.
>
> Works with Java7 and maven 3.3.1, 3.3.3, 3.3.9.
>
> The integration
That's weird. I don't see this... I'm on Linux, too.
Works with Java7 and maven 3.3.1, 3.3.3, 3.3.9.
The integration job seems to be ok, too:
https://builds.apache.org/job/maven-plugins-ITs-m3/
Am 13.10.2016 um 19:43 schrieb Hervé BOUTEMY:
> I built the release and got a failure in an IT:
>
I built the release and got a failure in an IT:
[INFO] Building: MPMD-187/pom.xml
[INFO] run script verify.groovy
[INFO] ..FAILED (4.4 s)
[INFO] The post-build script did not succeed. assert !pmdXml.exists()
|| |
|| true
the issue is not to merge blindly any request: it is to check the content, if
it is not too specific to a user, if there is IT, etc...
then if you'd like to help, yes, we're interested to help you become a
committer: you'll need to gain merit by taking a PR, check that it looks ok to
you then
I ll be happy to help committing those patches in other repository. How
could I get write access to it. Any suggestion?
On Oct 8, 2016 2:39 AM, "Robert Scholte" wrote:
Hi,
it is not possible to merge these pullrequests at github, it is a read-only
clone. And in case of the
+1 (binding)
Even if you key is available in public, you must/should add your key here
https://dist.apache.org/repos/dist/release/maven/KEYS
On 11 October 2016 at 05:15, Andreas Dangel wrote:
> Hi,
>
> We solved 11 issues:
>
+1 (non-binding)
The timeframe for voting ends today... Is there anything, that should be
done on my end? Or got the email just lost between the other mails?
It's the first time I'm staging a release ;)
Regards,
Andreas
Am 10.10.2016 um 20:15 schrieb Andreas Dangel:
> Hi,
>
> We solved
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/127
@britter No big problem. Can you always run build locally? AFAIK your PC is
running the build two hours. Normally 45 minutes in Jenkins and my PC Intel i7
4Core 3GHz SSD disk.
---
If your
Github user vaimr commented on the issue:
https://github.com/apache/maven-surefire/pull/122
The problem is that no surefire stores information about the test execution
time. I build tests in Jenkins pipeline script. He balances the tests by
run-time, breaks it into several blocks and
GitHub user britter opened a pull request:
https://github.com/apache/maven-surefire/pull/128
Unpack Suffix for parameterized JUnit4VersionsIT
As discussed in #126 : Pass suffix parameter to unpack method in order to
generate separate test workspaces.
You can merge this pull
Hi Alix,
Thanks for the patch: I'll review it this WE.
See you soon at next Paris Hackergarten Meetup :)
http://www.meetup.com/fr-FR/Paris-Hackergarten/
If other people near Paris are interested, don't hesitate to come also.
And if other Maven devs are involved in equivalent meetings in other
Tibor Digana schrieb am Di., 11. Okt. 2016 um
10:01 Uhr:
> Both old Jenkins builds [1] already use JDK 8.
> So this should not be a problem.
>
Perfect! I have something put together in a local branch. I think you're
going to like it :-)
>
> [1]
>
Hello Tibor,
okay, I will prepare something, after we have integrated the parameterized
JUnit4VersionsIT into junit5 branch.
Tibor Digana schrieb am Di., 11. Okt. 2016 um
19:50 Uhr:
> Sorry for my typos, again:
> *Maybe we should setup second trigger in Jenkins build
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/127
> I fixed this issue where I removed [1]
Thank you!
> Because of one method in commons-lang3 we should not pass such a big
library.
ACK
> Instead I created
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/126
@Tibor17 Wouldn't it be better to rebase junit5 branch onto master? I don't
have push access to maven-surefire, so you would have to do the trick.
---
If your project is set up for it, you
28 matches
Mail list logo