jbosscache-core-3.2.8.GA/ 0000755 0001750 0001750 00000000000 11675222145 014731 5 ustar moeller moeller jbosscache-core-3.2.8.GA/README-COMMITTERS.txt 0000644 0001750 0001750 00000001167 11111047320 020101 0 ustar moeller moeller Before committing anything, PLEASE make sure you have the following in your ~/.subversion/config.
This will ensure files have the *correct* line endings. Note: we do not use native since cygwin
users like LF endings. Also be sure that your IDE uses this config:
[miscellany]
enable-auto-props = yes
[auto-props]
*.java = svn:keywords=Id Revision;svn:eol-style=LF
*.xml = svn:keywords=Id Revision;svn:eol-style=LF
*.wsdl = svn:keywords=Id Revision;svn:eol-style=LF
*.xsd = svn:keywords=Id Revision;svn:eol-style=LF
*.txt = svn:keywords=Id Revision;svn:eol-style=LF
*.sh = svn:keywords=Id Revision;svn:eol-style=LF;svn:executable
jbosscache-core-3.2.8.GA/README-Maven.txt 0000644 0001750 0001750 00000021762 11363357042 017502 0 ustar moeller moeller
1. WORKING WITH MAVEN
=====================
Requirements:
* Java 5.0 and above
* Maven 2.0.8 and above
1.1. Quickstart: Typical lifecycle phases
-----------------------------------------
Maven will create a target/ directory under the root for the creation of
output at every stage.
* mvn clean: Cleans out any old builds and binaries
* mvn compile: Compiles java source code.
* mvn test: Runs the TestNG unit test suite on the compiled code. Will also compile the tests. See the testing section
below for more information on running different test groups. The default test groups run are the "unit" and "functional".
* mvn package: Packages the module as a JAR file, the resulting JAR file will be in target/
* mvn package -Dmaven.test.skip=true: Creates a JAR file without running tests.
* mvn package -P Docs: Packages the module as a JAR file, and builds the javadocs and user documentation from docbook sources.
Important! Please note that if you try to generate user documentation using OpenJDK (at least build 14.0-b15) you might see an
exception like this:
java.lang.NullPointerException
at org.apache.fop.render.pdf.FopPDFImage.setup(FopPDFImage.java:144)
at org.apache.fop.pdf.PDFDocument.addImage(PDFDocument.java:794)
at org.apache.fop.render.pdf.PDFRenderer.putImage(PDFRenderer.java:1725)
at org.apache.fop.render.pdf.PDFRenderer.renderImage(PDFRenderer.java:1652)
...
This appears to be a known issue: https://lists.launchpad.net/openjdk/msg00820.html. To get around the issue, simply switch
to Sun JDK 5 or 6 to generate documentation.
* mvn install: will install the artifacts in your local repo for use by other projects (such as JBoss Cache POJO edition
which depends on JBoss Cache Core). Will also use Maven's assembly plugin to build ZIP files for download
(in target/distribution)
* mvn deploy: will build and deploy the project to the JBoss snapshots repository. Note that you should have your WebDAV
username and password set up. (Deploys snapshots to http://snapshots.jboss.org/maven2/org/jboss/cache/). If you have
a non-SNAPSHOT version number in your pom.xml, it will be deployed to the live releases repository (see below)
* mvn clean site -Ptest-functional,codeCoverage: will run all tests in the test-functional profile and generate code
coverage reports using EMMA.
1.2. Setting up your username and password to make releases and shapshot release
--------------------------------------------------------------------------------
You will also have to configure maven to use your username and password to access the repository. For this, you will
have to modify the servers section of maven settings file ($MAVEN_HOME/conf/settings.xml, or ~/.m2/settings.xml).
Something similar to the following should be added:
...
...
jboss-developer
jboss.org username
jboss.org password
jboss-snapshots
jboss.org username
jboss.org password
jboss-releases
jboss.org username
jboss.org password
...
...
1.3. Deploying a release to a live repository
---------------------------------------------
Very simple. Make sure you have the version number in your pom.xml set to a non-SNAPSHOT version. Maven will pick up
on this and deploy to your release repository rather than the snapshot repository.
The JBoss repository will hold this release in a staging directory which can be accessed by logging in to
https://repository.jboss.org/nexus
After verifying the POM and the artifacts in Nexus, you can then close the repository and push the relase live.
2. TESTING
==========
Tests are written against the TestNG testing framework. Each test should belong to one or more group. The group acts as
a filter, and is used to select which tests are ran as part of the maven test lifecycle. There are 3 groups that are
currently in use, but there is not formal, you can make up any group name if you like.
2.1. Current Groups
-------------------
* unit - Unit tests using stubs to isolate and test each major class in JBoss Cache. This is the default group run if no test group is specified.
* functional - Tests which test the general functionality of JBoss Cache
* jgroups - Tests which need to send data on a JGroups Channel
* transaction - Tests which use a transaction manager
* profiling - Tests used for manual profiling, not meant for automated test runs
* manual - Other tests that are run manually
* integration - Integration tests emulating usage patterns for specific products such as JBoss AS Clustering and Hibernate clustering
It should be noted that every test (except those not intended to be run by Hudson) should at least be in the functional
group, since this is the default test group that is executed by maven, and the one that is required to prepare a release.
2.2. Executing the default test run
-----------------------------------
The default run executes all tests in the functional group. To just run the tests with txt and xml output the command is:
$ mvn test
Alternatively, you can execute the tests AND generate a report with:
$ mvn surefire-report:report
If you already have ran a test cycle, and you want to generate a report off the current reports, then you use the
report-only goal, ike so:
$ mvn surefire-report:report-only
2.3. Executing different groups
-------------------------------
A group can be executed (using the default configuration) by simply using the appropriate profile, like so:
$ mvn -P test-jgroups test
2.4. Executing a single test
----------------------------
A single test can be executed using the test property. The value is the short name (not the fully qualified package name)
of the test.
$ mvn -P test-XXX -Dtest=FqnTest test
Alternatively, if there is more than one test with a given classname in your test suite, you could provide the path to
the test.
$ mvn -P test-XXX -Dtest=org/jboss/cache/multiplexer/SyncReplTxTest test
2.5. Executing all tests in a given package
--------------------------------------------
This can be achieved by passing in the package name with a wildcard to the test parameter.
$ mvn -P test-XXX -Dtest=org/jboss/cache/multiplexer/* test
2.6. Skipping the test run
--------------------------
It is sometimes desirable to install the jboss cache package in your local repository without performing a full test run.
To do this, simply use the maven.test.skip.exec property:
$ mvn -Dmaven.test.skip.exec=true install
Again, this is just a shortcut for local use. It SHOULD NEVER BE USED when releasing. Also, make sure "exec" is included
in the property, if not the tests will not be built, which will prevent a test jar being produced (POJO Cache needs the
Core Cache test jar).
2.7. Permutations
-----------------
We use the term permutation to describe a group execution against a particular config. This allows us to test a variety
of environments and configurations without rewriting the same basic test over and over again. For example, the jgroups-tcp
permutation executes the jgroups group using the TCP config. Each permutation requires a maven profile which defines the
various options, environmental variables, etc. The command to run the jgroups-tcp permutatin is:
$ mvn -Pjgroups-tcp surefire-report:report
Each permutation uses its own report directory, and its own html output file name. This allows you to execute multiple
permutations without wiping the results from the previous run. Note that due to the way maven operates, only one
permutation can be executed per mvn command. So automating multiple runs requires shell scripting, or some other execution
framework to make multiple called to maven.
2.8. Running permutations manually or in an IDE
-----------------------------------------------
Sometimes you want to run a test using settings other than the defaults (such as UDP for "jgroups" group tests or the
DummyTransactionManager for "transaction" group tests). This can be achieved by referring to the Maven POM file
to figure out which system properties are passed in to the test when doing something different.
E.g., to run a "jgroups" group test in your IDE using TCP instead of the default UDP, set the following:
-Djgroups.stack=tcp
Or, to use JBoss JTA (Arjuna TM) instead of the DummyTransactionManager in a "transaction" group test, set:
-Dorg.jboss.cache.test.tm=jboss-jta
Please refer to the POM file for more properties and permutations.
2.9. Integration with CruiseControl / Hudson
--------------------------------------------
CruiseControl should do the following:
* Run "mvn clean site" - will clean and run tests, and then prepare reports. In addition to unit tests, this project is
set up to run FindBugs, PMD, jxr, and a bunch of other code analysis tools and provide a report in
target/site/project-reports.html - which should be linked from the CruiseControl summary page.
jbosscache-core-3.2.8.GA/assembly/ 0000755 0001750 0001750 00000000000 11675221271 016547 5 ustar moeller moeller jbosscache-core-3.2.8.GA/assembly/assembly-1.1.0-SNAPSHOT.xsd 0000644 0001750 0001750 00000173017 11057166721 023011 0 ustar moeller moeller
1.0.0+
An assembly defines a collection of files usually distributed in an
archive format such as zip, tar, or tar.gz that is generated from a
project. For example, a project could produce a ZIP assembly which
contains a project's JAR artifact in the root directory, the
runtime dependencies in a lib/ directory, and a shell script to launch
a stand-alone application.
1.0.0+
An assembly defines a collection of files usually distributed in an
archive format such as zip, tar, or tar.gz that is generated from a
project. For example, a project could produce a ZIP assembly which
contains a project's JAR artifact in the root directory, the
runtime dependencies in a lib/ directory, and a shell script to launch
a stand-alone application.
1.0.0+
Sets the id of this assembly. This is a symbolic name for a
particular assembly of files from this project. Also, aside from
being used to distinctly name the assembled package by attaching
its value to the generated archive, the id is used as your
artifact's classifier when deploying.
1.0.0+
Specifies the formats of the assembly. Multiple formats can be
supplied and the Assembly Plugin will generate an archive for each
desired formats. When deploying your project, all file formats
specified will also be deployed. A format is specified by supplying
one of the following values in a <format> subelement:
<ul>
<li><b>"zip"</b> - Creates a ZIP file format</li>
<li><b>"gz"</b> - Creates a GZIP format</li>
<li><b>"tar"</b> - Creates a TAR format</li>
<li><b>"tar.gz"</b> - Creates a gzip'd TAR format</li>
<li><b>"tar.bz2</b> - Creates a bzip'd TAR format</li>
</ul>
0.0.0+
Includes a base directory in the final archive. For example,
if you are creating an assembly named "your-app", setting
includeBaseDirectory to true will create an archive that
includes this base directory. If this option is set to false
the archive created will unzip its content to the current
directory. Default value is true.
1.1.0
Sets the base directory of the resulting assembly archive. If this is not
set and includeBaseDirectory == true, ${project.build.finalName} will be used instead.
0.0.0+
Includes a site directory in the final archive. The site directory
location of a project is determined by the siteDirectory parameter
of the Assembly Plugin. Default value is false.
1.0.0+
Specifies which module files to include in the assembly. A moduleSet
is specified by providing one or more of <moduleSet>
subelements.
1.0.0+
Specifies which groups of files to include in the assembly. A
fileSet is specified by providing one or more of <fileSet>
subelements.
1.0.0+
Specifies which single files to include in the assembly. A file
is specified by providing one or more of <file>
subelements.
1.0.0+
Specifies which dependencies to include in the assembly. A
dependencySet is specified by providing one or more of
<dependencySet> subelements.
1.0.0+
Specifies which repository files to include in the assembly. A
repository is specified by providing one or more of
<repository> subelements.
1.0.0+
Specifies the shared components xml file locations to include in the
assembly. The locations specified must be relative to the basedir of
the project. When multiple componentDescriptors are found, their
contents are merged. Check out the <a href="component.html">
descriptor components</a> for more information. A
componentDescriptor is specified by providing one or more of
<componentDescriptor> subelements.
1.0.0+
Defines a Maven repository to be included in the assembly. The artifacts
available to be included in a repository are your project's dependency
artifacts. The repository created contains the needed metadata entries
and also contains both sha1 and md5 checksums. This is useful for creating
archives which will be deployed to internal repositories.
<br/><b>NOTE:</b> Currently, only artifacts from the central repository
are allowed.
1.0.0+
If set to true, this property will trigger the creation of repository
metadata which will allow the repository to be used as a functional remote
repository. Default value is false.
1.0.0+
Specifies that you want to align a group of artifacts to a specified
version. A groupVersionAlignment is specified by providing one or
more of <groupVersionAlignment> subelements.
1.1.0
Specifies the scope for artifacts included in this repository.
Default scope value is "runtime".
1.1.0
When specified as true, any include/exclude patterns which aren't used to filter an actual
artifact during assembly creation will cause the build to fail with an error. This is meant
to highlight obsolete inclusions or exclusions, or else signal that the assembly descriptor
is incorrectly configured.
1.1.0
Whether standard exclusion patterns, such as those matching CVS and Subversion
metadata files, should be used when calculating the files affected by this set.
For backward compatibility, the default value is true.
1.0.0+
Sets the output directory relative to the root
of the root directory of the assembly. For example,
"log" will put the specified files in the log directory.
1.0.0+
When <include> subelements are present, they define a set of
files and directory to include. If none is present, then
<includes> represents all valid values.
1.0.0+
When <exclude> subelements are present, they define a set of
files and directory to exclude. If none is present, then
<excludes> represents no exclusions.
1.0.0+
Similar to a UNIX permission, sets the file mode of the files included.
Format: (User)(Group)(Other) where each component is a sum of Read = 4,
Write = 2, and Execute = 1. For example, the default value of 0644
translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Similar to a UNIX permission, sets the directory mode of the directories
included. Format: (User)(Group)(Other) where each component is a sum of
Read = 4, Write = 2, and Execute = 1. For example, the default value of
0755 translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Allows a group of artifacts to be aligned to a specified version.
1.0.0+
The groupId of the artifacts for which you want to align the
versions.
1.0.0+
The version you want to align this group to.
1.0.0+
When <exclude> subelements are present, they define the
artifactIds of the artifacts to exclude. If none is present, then
<excludes> represents no exclusions. An exclude is specified
by providing one or more of <exclude> subelements.
1.0.0+
A dependencySet allows inclusion and exclusion of project dependencies
in the assembly.
1.0.0+
Sets the mapping pattern for all dependencies included in this
assembly. Default is ${artifactId}-${version}.${extension}.
1.0.0+
If set to true, this property will unpack all dependencies
into the specified output directory. When set to false
dependencies will be includes as archives (jars). Can only unpack
jar, zip, tar.gz, and tar.bz archives. Default value is false.
1.1.0
Allows the specification of includes and excludes, along with filtering options, for items
unpacked from a dependency artifact.
1.0.0+
Sets the dependency scope for this dependencySet.
Default scope value is "runtime".
1.1.0
When specified as true, any include/exclude patterns which aren't used to filter an actual
artifact during assembly creation will cause the build to fail with an error. This is meant
to highlight obsolete inclusions or exclusions, or else signal that the assembly descriptor
is incorrectly configured.
1.1.0
Whether standard exclusion patterns, such as those matching CVS and Subversion
metadata files, should be used when calculating the files affected by this set.
For backward compatibility, the default value is true.
1.0.0+
Sets the output directory relative to the root
of the root directory of the assembly. For example,
"log" will put the specified files in the log directory.
1.0.0+
When <include> subelements are present, they define a set of
files and directory to include. If none is present, then
<includes> represents all valid values.
1.0.0+
When <exclude> subelements are present, they define a set of
files and directory to exclude. If none is present, then
<excludes> represents no exclusions.
1.0.0+
Similar to a UNIX permission, sets the file mode of the files included.
Format: (User)(Group)(Other) where each component is a sum of Read = 4,
Write = 2, and Execute = 1. For example, the default value of 0644
translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Similar to a UNIX permission, sets the directory mode of the directories
included. Format: (User)(Group)(Other) where each component is a sum of
Read = 4, Write = 2, and Execute = 1. For example, the default value of
0755 translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.1.0
Specifies options for including/excluding/filtering items extracted from an archive.
1.1.0
Set of patterns for matching items to be included from an archive as it is unpacked.
1.1.0
Set of patterns for matching items to be excluded from an archive as it is unpacked.
1.1.0
Whether to filter symbols in the files as they are unpacked from the archive, using
properties from the build configuration.
1.0.0+
A moduleSet represent one or more project <module> present inside
a project's pom.xml. This allows you to include sources or binaries
belonging to a project's <modules>.
<br/><b>NOTE:</b> When using <moduleSets> from the command-line, it
is required to pass first the package phase by doing: "mvn package
assembly:assembly". This bug/issue is scheduled to be addressed by Maven 2.1.
1.1.0
If set to false, the plugin will exclude sub-modules from processing in this ModuleSet.
Otherwise, it will process all sub-modules, each subject to include/exclude rules.
Default value is true.
1.0.0+
This is a list of <include/> subelements, each containing a
module reference of the type groupId:artifactId. Modules matching
these elements will be included in this set. If none is present,
then <includes> represents all valid values.
1.0.0+
This is a list of <exclude/> subelements, each containing a
module reference of the type groupId:artifactId. Modules matching
these elements will be excluded from this set.
1.0.0+
When this is present, the plugin will include the source files of
the included modules from this set in the resulting assembly.
1.0.0+
When this is present, the plugin will include the binaries of the
included modules from this set in the resulting assembly.
1.0.0+
Contains configuration options for including the source files of a
project module in an assembly.
1.1.0
Specifies which groups of files from each included module to include in the assembly. A
fileSet is specified by providing one or more of <fileSet> subelements.
1.1.0
Specifies whether the module's finalName should be prepended to the outputDirectory
values of any fileSets applied to it. Default value is true.
1.1.0
Specifies whether sub-module directories below the current module should be excluded
from fileSets applied to that module. This might be useful if you only mean to copy
the sources for the exact module list matched by this ModuleSet, ignoring (or processing
separately) the modules which exist in directories below the current one.
Default value is true.
1.1.0
Sets the mapping pattern for all module base-directories included in this assembly.
NOTE: This field is only used if includeModuleDirectory == true.
Default is the module's ${artifactId}.
1.1.0
When specified as true, any include/exclude patterns which aren't used to filter an actual
artifact during assembly creation will cause the build to fail with an error. This is meant
to highlight obsolete inclusions or exclusions, or else signal that the assembly descriptor
is incorrectly configured.
1.1.0
Whether standard exclusion patterns, such as those matching CVS and Subversion
metadata files, should be used when calculating the files affected by this set.
For backward compatibility, the default value is true.
1.0.0+
Sets the output directory relative to the root
of the root directory of the assembly. For example,
"log" will put the specified files in the log directory.
1.0.0+
When <include> subelements are present, they define a set of
files and directory to include. If none is present, then
<includes> represents all valid values.
1.0.0+
When <exclude> subelements are present, they define a set of
files and directory to exclude. If none is present, then
<excludes> represents no exclusions.
1.0.0+
Similar to a UNIX permission, sets the file mode of the files included.
Format: (User)(Group)(Other) where each component is a sum of Read = 4,
Write = 2, and Execute = 1. For example, the default value of 0644
translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Similar to a UNIX permission, sets the directory mode of the directories
included. Format: (User)(Group)(Other) where each component is a sum of
Read = 4, Write = 2, and Execute = 1. For example, the default value of
0755 translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
A fileSet allows the inclusion of groups of files into the assembly.
1.0.0+
Sets the absolute or relative location from the module's
directory. For example, "src/main/bin" would select this
subdirectory of the project in which this dependency is defined.
1.0.0+
Sets the line-endings of the files in this fileSet.
Valid values:
<ul>
<li><b>"keep"</b> - Preserve all line endings</li>
<li><b>"unix"</b> - Use Unix-style line endings</li>
<li><b>"lf"</b> - Use a single line-feed line endings</li>
<li><b>"dos"</b> - Use DOS-style line endings</li>
<li><b>"crlf"</b> - Use Carraige-return, line-feed line endings</li>
</ul>
1.1.0
Whether to filter symbols in the files as they are copied, using
properties from the build configuration.
1.1.0
When specified as true, any include/exclude patterns which aren't used to filter an actual
artifact during assembly creation will cause the build to fail with an error. This is meant
to highlight obsolete inclusions or exclusions, or else signal that the assembly descriptor
is incorrectly configured.
1.1.0
Whether standard exclusion patterns, such as those matching CVS and Subversion
metadata files, should be used when calculating the files affected by this set.
For backward compatibility, the default value is true.
1.0.0+
Sets the output directory relative to the root
of the root directory of the assembly. For example,
"log" will put the specified files in the log directory.
1.0.0+
When <include> subelements are present, they define a set of
files and directory to include. If none is present, then
<includes> represents all valid values.
1.0.0+
When <exclude> subelements are present, they define a set of
files and directory to exclude. If none is present, then
<excludes> represents no exclusions.
1.0.0+
Similar to a UNIX permission, sets the file mode of the files included.
Format: (User)(Group)(Other) where each component is a sum of Read = 4,
Write = 2, and Execute = 1. For example, the default value of 0644
translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Similar to a UNIX permission, sets the directory mode of the directories
included. Format: (User)(Group)(Other) where each component is a sum of
Read = 4, Write = 2, and Execute = 1. For example, the default value of
0755 translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Contains configuration options for including the binary files of a
project module in an assembly.
1.1.0
When specified, the attachmentClassifier will cause the assembler to look at artifacts
attached to the module instead of the main project artifact. If it can find an attached
artifact matching the specified classifier, it will use it; otherwise, it will throw an
exception.
1.0.0+
If set to true, the plugin will include the direct and transitive dependencies of
of the project modules included here. Otherwise, it will only include the module
packages only. Default value is true.
1.1.0
Specifies which dependencies of the module to include in the assembly. A
dependencySet is specified by providing one or more of
<dependencySet> subelements.
1.0.0+
If set to true, this property will unpack all module packages
into the specified output directory. When set to false
module packages will be included as archives (jars).
Default value is true.
1.1.0
Allows the specification of includes and excludes, along with filtering options, for items
unpacked from a module artifact.
1.0.0+
Sets the mapping pattern for all dependencies included
in this assembly.
Default is ${artifactId}-${version}.${extension}.
1.1.0
When specified as true, any include/exclude patterns which aren't used to filter an actual
artifact during assembly creation will cause the build to fail with an error. This is meant
to highlight obsolete inclusions or exclusions, or else signal that the assembly descriptor
is incorrectly configured.
1.1.0
Whether standard exclusion patterns, such as those matching CVS and Subversion
metadata files, should be used when calculating the files affected by this set.
For backward compatibility, the default value is true.
1.0.0+
Sets the output directory relative to the root
of the root directory of the assembly. For example,
"log" will put the specified files in the log directory.
1.0.0+
When <include> subelements are present, they define a set of
files and directory to include. If none is present, then
<includes> represents all valid values.
1.0.0+
When <exclude> subelements are present, they define a set of
files and directory to exclude. If none is present, then
<excludes> represents no exclusions.
1.0.0+
Similar to a UNIX permission, sets the file mode of the files included.
Format: (User)(Group)(Other) where each component is a sum of Read = 4,
Write = 2, and Execute = 1. For example, the default value of 0644
translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Similar to a UNIX permission, sets the directory mode of the directories
included. Format: (User)(Group)(Other) where each component is a sum of
Read = 4, Write = 2, and Execute = 1. For example, the default value of
0755 translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
A file allows individual file inclusion with the option to change
the destination filename not supported by fileSets.
1.0.0+
Sets the absolute or relative path from the module's directory
of the file to be included in the assembly.
1.0.0+
Sets the output directory relative to the root
of the root directory of the assembly. For example,
"log" will put the specified files in the log directory.
1.0.0+
Sets the destination filename in the outputDirectory.
Default is the same name as the source's file.
1.0.0+
Similar to a UNIX permission, sets the file mode of the files included.
Format: (User)(Group)(Other) where each component is a sum of Read = 4,
Write = 2, and Execute = 1. For example, the default value of 0644
translates to User read-write, Group and Other read-only.
<a href="http://www.onlamp.com/pub/a/bsd/2000/09/06/FreeBSD_Basics.html">(more on
unix-style permissions)</a>
1.0.0+
Sets the line-endings of the files in this file.
Valid values are:
<ul>
<li><b>"keep"</b> - Preserve all line endings</li>
<li><b>"unix"</b> - Use Unix-style line endings</li>
<li><b>"lf"</b> - Use a single line-feed line endings</li>
<li><b>"dos"</b> - Use DOS-style line endings</li>
<li><b>"crlf"</b> - Use Carraige-return, line-feed line endings</li>
</ul>
1.0.0+
Sets whether to determine if the file is filtered.