Hi,

based on that problem (and feedback during the dev hangout) i have created an infrastructure issue ...

https://issues.apache.org/jira/browse/INFRA-8491

On 10/16/14 7:23 AM, Hervé BOUTEMY wrote:
Hi,

Yes, I'm puzzled with that too: are there internal site mirrors accessible
from ASF Jenkins?
probably something for INFRA Jira issue...

Regards,

Hervé

Le mercredi 15 octobre 2014 13:16:37 Karl Heinz Marbaise a écrit :
Hi,

just a question cause currently the dist-tool fails with messages about
versions which can't be found like

maven-war-plugin 2.4 instead 2.5...

[INFO] Generating "Dist Tool> Check Index Pages" report ---
dist-tool-plugin:1.0-SNAPSHOT:check-index-page
[ERROR] maven-compiler-plugin: found 3.1 instead of 3.2 in
http://maven.apache.org/plugins/
[ERROR] maven-linkcheck-plugin: found 1.1 instead of 1.2 in
http://maven.apache.org/plugins/
[ERROR] maven-source-plugin: found 2.3 instead of 2.4 in
http://maven.apache.org/plugins/
[ERROR] maven-war-plugin: found 2.4 instead of 2.5 in
http://maven.apache.org/plugins/
[INFO] Generating "Dist Tool> Plugins Prerequisites" report ---
dist-tool-plugin:1.0-SNAPSHOT:check-prerequisites-site
[INFO] Generating "Failure Hack" report         ---
dist-tool-plugin:1.0-SNAPSHOT:failure-report
[ERROR] check-index-page.log error log not empty:
maven-compiler-plugin: found 3.1 instead of 3.2 in
http://maven.apache.org/plugins/
maven-linkcheck-plugin: found 1.1 instead of 1.2 in
http://maven.apache.org/plugins/
maven-source-plugin: found 2.3 instead of 2.4 in
http://maven.apache.org/plugins/
maven-war-plugin: found 2.4 instead of 2.5 in
http://maven.apache.org/plugins/



Is there something related to some mirrors which are not synched
correctly ? I observed same things from my working desk...and from my
notebook via mobile phone internet access...

Kind regards
Karl Heinz Marbaise


Kind regards
Karl Heinz Marbaise




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to