ok, I didn't update my repo clone: now the run-its profile is activated
then the plan should just confirm "it works!" :)
and find which jobs are special, like maven-dist-tool (which has to be
scheduled daily instead of code change, and one platform only)
Regards,
Hervé
Le mercredi 6 décembre
Github user olamy commented on the issue:
https://github.com/apache/maven-wagon/pull/37
interesting feature. I wonder you could add some documentation maybe here:
http://maven.apache.org/wagon/wagon-providers/wagon-http/
---
--
On Wed 6 Dec 2017 at 22:38, Hervé BOUTEMY wrote:
> Now that we have 2 ASF Organization Jenkins jobs (one for gitbox [1] and
> one
> for git-wip: thank you Stephen) and that it looks quite successful, let's
> plan
> the next steps.
>
> Here is what I see:
> 1. removal of hand-defined Jenkins jobs
Now that we have 2 ASF Organization Jenkins jobs (one for gitbox [1] and one
for git-wip: thank you Stephen) and that it looks quite successful, let's plan
the next steps.
Here is what I see:
1. removal of hand-defined Jenkins jobs that are now duplicates
2. preparation of the 60 new empty git
don-vip opened a new pull request #9: upgrade to ASM 6.0 (final)
URL: https://github.com/apache/maven-plugin-tools/pull/9
The ALPHA dependency causes problems to projects using Enforcer rules, see
https://github.com/jenkinsci/jacoco-plugin/pull/92#issuecomment-349457441
---
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.0.0
This plugin uses the Javadoc tool to generate javadocs for the specified
project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project
Hi,
The vote has passed with the following result:
+1 : Mark Raynsford, Robert Scholte, Hervé BOUTEMY, Olivier Lamy
PMC quorum: reached
I will promote the artifacts to the central repo.
On Sun, 03 Dec 2017 22:50:42 +0100, Robert Scholte
wrote:
Hi,
We solved 27 issues:
https://issues.ap
Github user rmannibucau commented on the issue:
https://github.com/apache/maven-wagon/pull/37
Small misunderstanding: default behavior is the current one but default
(same for standard) clasq value actually references the name of the impl -
with a shortname to be human feiendly - a
Github user jkff commented on the issue:
https://github.com/apache/maven-wagon/pull/37
Wait: the default one would give current behavior, which doesn't retry on
socket errors. Did you mean `-Dmaven.wagon.http.retryhandler.class=standard`
perhaps, and without the `nonRetryableClasses`
+1
On 4 December 2017 at 08:50, Robert Scholte wrote:
> Hi,
>
> We solved 27 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317529&version=12330875&styleName=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=pr
Hi,
I would lke to use the categories facility with JUnit 4.12 in a reactor
project, I am finding some issue, but they seem to me so basic that maybe
it is only a lack of documentation or that we can provide some minor fix in
order to make life easier:
1) In a reactor a would like to run mvn test
11 matches
Mail list logo
