Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/148
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/30)
---
-
To unsubscribe, e-mai
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/148
[MNG-5600] Dependency management import should support exclusions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/mave
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/147
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/29)
---
-
To unsubscribe, e-mai
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/147
[MNG-5527] Dependency management import should support relocations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChristianSchulte/mav
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/146
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/28)
---
-
To unsubscribe, e-mai
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven/pull/146
[MNG-4463] Dependency management import should support version ranges.
Closes #64 without merging. ITs are pending to be committed.
You can merge this pull request into a Git repository by r
Github user ChristianSchulte commented on the issue:
https://github.com/apache/maven/pull/143
[Corresponding IT pull
request.](https://github.com/apache/maven-integration-testing/pull/27)
---
-
To unsubscribe, e-mai
+1
On 29 December 2017 at 03:20, Hervé BOUTEMY wrote:
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317923&version=12338726&styleName=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=pro
Le dimanche 31 décembre 2017, 00:04:59 CET Olivier Lamy a écrit :
> works fine (on my machine :-) )
> OSX + java 1.8.0_121
ok, I had a deeper look: the IT expects a warning that exists with Java 8
(missing @param) but not Java 7 (more permissive on documentation)
I added a serialwarn: this causes
works fine (on my machine :-) )
OSX + java 1.8.0_121
Well TBH I'm a bit lost with Jenkins result display
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-javadoc-plugin/job/master/
what are all the open tasks links?
I'm even more lost If I look at a build result
https://
Hi Hervé,
merge result is as expected.
Thanks a lot!
Robert
On Sat, 30 Dec 2017 10:51:06 +0100, Hervé BOUTEMY
wrote:
merge done: can you check it's as you expected?
notice that if you have failing IT on MJAVADOC-508 like I have locally,
it's
not the merge but it was already present be
+1 to merge with the latest commits.
Robert
On Sat, 30 Dec 2017 19:12:31 +0100, Robert Scholte
wrote:
Hi Karl Heinz,
Please verify my commit.
thanks,
Robert
On Sat, 30 Dec 2017 18:36:29 +0100, Karl Heinz Marbaise
wrote:
Hi,
On 30/12/17 18:33, Robert Scholte wrote:
Sure, let me
Yep, if you can confirm the jobs are covered by the TLP Jenkins script,
then they can be removed.
I don't think there's a reason to keep the historic statistics.
+1
Robert
On Sat, 30 Dec 2017 19:14:34 +0100, Karl Heinz Marbaise
wrote:
Hi,
based on the new Jenkinsfile based Builds I wil
Hi,
based on the new Jenkinsfile based Builds I will delete step by step
older jobs for example:
https://builds.apache.org/job/maven-enforcer/
cause we have now as replacements..
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-enforcer/
Any objects about that?
Kind r
Hi Karl Heinz,
Please verify my commit.
thanks,
Robert
On Sat, 30 Dec 2017 18:36:29 +0100, Karl Heinz Marbaise
wrote:
Hi,
On 30/12/17 18:33, Robert Scholte wrote:
Sure, let me pick this up
I have already implemented different solutions but based on performance
measurements the one
Hi,
On 30/12/17 18:33, Robert Scholte wrote:
Sure, let me pick this up
I have already implemented different solutions but based on performance
measurements the one I have implemented seemed to be the fastest
solution ?...
Kind regards
Karl Heinz Marbaise
Robert
On Sat, 30 Dec 2017 15:
Sure, let me pick this up
Robert
On Sat, 30 Dec 2017 15:15:41 +0100, Karl Heinz Marbaise
wrote:
Hi Robert,
On 29/12/17 11:18, Robert Scholte wrote:
Hi Karl Heinz,
I think the REgExp usage can be improved.
Now it used for building up a new String followed by searching, I would
expect t
thank you Plamen: this script is really awesome!
I reworked it a little bit and just added it to our svn git migration scripts
area [1]
And I just pushed the result on maven-acr-plugin: you can see the result live.
As you can see, the tags on GitBox [2] are updated but not the tags on GitHub
[3
Hi Robert,
On 29/12/17 11:18, Robert Scholte wrote:
Hi Karl Heinz,
I think the REgExp usage can be improved.
Now it used for building up a new String followed by searching, I would
expect that searching for ${(.+)} groups to be more efficient.
Do you have some suggestions what you exactly ha
merge done: can you check it's as you expected?
notice that if you have failing IT on MJAVADOC-508 like I have locally, it's
not the merge but it was already present before
@Olivier: I don't know in which conditions you tested MJAVADOC-508, but it is
failing for me: Linux+Java 7
Regards,
Herv
20 matches
Mail list logo
