/********************************************************************************
* CruiseControl, a Continuous Integration Toolkit
* Copyright (c) 2007, ThoughtWorks, Inc.
* 200 E. Randolph, 25th Floor
* Chicago, IL 60601 USA
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* + Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* + Redistributions in binary form must reproduce the above
* copyright notice, this list of conditions and the following
* disclaimer in the documentation and/or other materials provided
* with the distribution.
*
* + Neither the name of ThoughtWorks, Inc., CruiseControl, nor the
* names of its contributors may be used to endorse or promote
* products derived from this software without specific prior
* written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
* PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
* LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
* NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
********************************************************************************/
package net.sourceforge.cruisecontrol.config;
import net.sourceforge.cruisecontrol.gendoc.annotations.Required;
/**
*
* <p>The <include.projects> tag is used to consolidate several configuration
* files into a single configuration. One advantage over using XML includes are that
* the target files are valid configuration files in their own right and not just XML
* fragments. Also, including projects using the tag is less fragile as an error in one
* file will not keep the rest of the projects for building.</p>
* <p>Configuration files included this way are processed with the properties and
* plugins defined in the main configuration file, which easily allows per instance
* configuration. Properties and plugins defined in the processed files are not made
* available outside the scope of that file.</p>
* <p>Project names must still remain unique. The first project with a given name will
* be loaded and any subsequent projects attempting to use the same name will be skipped.</p>
*/
public class IncludeProjectsPlugin {
private String file;
/**
* @param file Relative path from current configuration file to the configuration file to process.
*/
@Required
public void setFile(String file) {
this.file = file;
}
public void validate() {
}
public String getFile() {
return file;
}
}