blob: 17fa4c3beaf753ff7be616d919a16e90c247ee4f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright (c) 2016 IBM Corporation and others.
All rights reserved. This program and the accompanying materials
are made available under the terms of the Eclipse Public License v1.0
which accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
Contributors:
David Williams - initial API and implementation
-->
<project
name="Eclipse summarize comparator logs"
default="compare">
<target
name="compare"
depends="checkAvailability, init"
if="propertyFileAvailable">
<echo message="Genererating comparator log summaries ..." />
<!--
we get these properties so we can print out the repository
used by comparator, 'comparator.repo'.
-->
<loadproperties srcfile="${buildDirectory}/mavenproperties.properties" />
<!--create html output for compile logs -->
<comparatorSummary
builddirectory="${buildDirectory}"
comparatorRepo="${comparator.repo}" />
</target>
<target
name="checkAvailability"
depends="init"
unless="propertyFileAvailable">
<echo message="WARNING: eclipse_compare not performed since property file did not exist: " />
<echo message=" ${buildDirectory}/mavenproperties.properties" />
</target>
<target
name="init"
unless="eclipse_compare.initialized">
<!--
if this property file is not available, that means some other part of the build
failed (or intentionally skipped) so there is no ability to do this task. Having
the explicit check here has advantage of avoiding error messages in error log.
-->
<available
file="${buildDirectory}/mavenproperties.properties"
property="propertyFileAvailable" />
<property
name="eclipse_compare.initialized"
value="true" />
</target>
</project>
|
