This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit d9ed3da91fe2e1ee6c663ae3334c88cbee5a53c3
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Tue Nov 3 21:45:24 2026 +0100

    Say that the filters and assembly directories are conventions only
    
    No plugin reads src/main/filters, src/test/filters or src/assembly
    unless the POM names the files there; the resources and assembly plugins
    have no default for them.
---
 .../introduction/introduction-to-the-standard-directory-layout.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git 
a/content/markdown/guides/introduction/introduction-to-the-standard-directory-layout.md
 
b/content/markdown/guides/introduction/introduction-to-the-standard-directory-layout.md
index 4cde0d24..0c452e35 100644
--- 
a/content/markdown/guides/introduction/introduction-to-the-standard-directory-layout.md
+++ 
b/content/markdown/guides/introduction/introduction-to-the-standard-directory-layout.md
@@ -27,18 +27,20 @@ The next section documents the directory layout expected by 
Maven and the direct
 
|:---------------------|:---------------------------------------------------------------------------|
 | `src/main/java`      | Application/Library sources                           
                     |
 | `src/main/resources` | Application/Library resources                         
                     |
-| `src/main/filters`   | Resource filter files                                 
                     |
+| `src/main/filters`   | Resource filter files (convention only, see below)    
                     |
 | `src/main/webapp`    | Web application sources                               
                     |
 | `src/test/java`      | Test sources                                          
                     |
 | `src/test/resources` | Test resources                                        
                     |
-| `src/test/filters`   | Test resource filter files                            
                     |
+| `src/test/filters`   | Test resource filter files (convention only, see 
below)                    |
 | `src/it`             | Integration Tests (primarily for plugins)             
                     |
-| `src/assembly`       | Assembly descriptors                                  
                     |
+| `src/assembly`       | Assembly descriptors (convention only, see below)     
                     |
 | `src/site`           | Site                                                  
                     |
 | `LICENSE.txt`        | Project's license                                     
                     |
 | `NOTICE.txt`         | Notices and attributions required by libraries that 
the project depends on |
 | `README.txt`         | Project's readme                                      
                     |
 
+Maven builds from `src/main/java`, `src/main/resources`, `src/test/java` and 
`src/test/resources` without any configuration, and the WAR, Invoker and Site 
plugins use `src/main/webapp`, `src/it` and `src/site` by default. 
`src/main/filters`, `src/test/filters` and `src/assembly` are only where these 
files conventionally go: no plugin reads them unless the POM names the files, 
the filters in `<build><filters>` (see [Filtering 
resources](../mini/guide-filtering-resources.html)) and the ass [...]
+
 At the top level, files descriptive of the project: a `pom.xml` file. In 
addition, there are textual documents meant for the user to be able to read 
immediately on receiving the source: `README.txt`, `LICENSE.txt`, etc.
 
 There are just two subdirectories of this structure: `src` and `target`. The 
only other directories that would be expected here are metadata like `CVS`, 
`.git` or `.svn`, and any subprojects in a multiproject build (each of which 
would be laid out as above).

Reply via email to