01: /********************************************************************************
02: * CruiseControl, a Continuous Integration Toolkit
03: * Copyright (c) 2007, ThoughtWorks, Inc.
04: * 200 E. Randolph, 25th Floor
05: * Chicago, IL 60601 USA
06: * All rights reserved.
07: *
08: * Redistribution and use in source and binary forms, with or without
09: * modification, are permitted provided that the following conditions
10: * are met:
11: *
12: * + Redistributions of source code must retain the above copyright
13: * notice, this list of conditions and the following disclaimer.
14: *
15: * + Redistributions in binary form must reproduce the above
16: * copyright notice, this list of conditions and the following
17: * disclaimer in the documentation and/or other materials provided
18: * with the distribution.
19: *
20: * + Neither the name of ThoughtWorks, Inc., CruiseControl, nor the
21: * names of its contributors may be used to endorse or promote
22: * products derived from this software without specific prior
23: * written permission.
24: *
25: * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
26: * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
27: * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
28: * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
29: * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
30: * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
31: * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
32: * PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
33: * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
34: * NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
35: * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
36: ********************************************************************************/package net.sourceforge.cruisecontrol.config;
37:
38: /**
39: *
40: * <p>The <include.projects> tag is used to consolidate several configuration
41: * files into a single configuration. One advantage over using XML includes are that
42: * the target files are valid configuration files in their own right and not just XML
43: * fragments. Also, including projects using the tag is less fragile as an error in one
44: * file will not keep the rest of the projects for building.</p>
45: * <p>Configuration files included this way are processed with the properties and
46: * plugins defined in the main configuration file, which easily allows per instance
47: * configuration. Properties and plugins defined in the processed files are not made
48: * available outside the scope of that file.</p>
49: * <p>Project names must still remain unique. The first project with a given name will
50: * be loaded and any subsequent projects attempting to use the same name will be skipped.</p>
51: */
52: public class IncludeProjectsPlugin {
53: private String file;
54:
55: /**
56: * Relative path from current configuration file to the configuration file to process.
57: * @param file
58: * @required
59: */
60: public void setFile(String file) {
61: this .file = file;
62: }
63:
64: public void validate() {
65: }
66:
67: public String getFile() {
68: return file;
69: }
70: }
|