You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kh...@apache.org on 2018/03/09 19:20:17 UTC
[maven-ear-plugin] branch MEAR-263 updated (1523046 -> fdb22b6)
This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch MEAR-263
in repository https://gitbox.apache.org/repos/asf/maven-ear-plugin.git.
discard 1523046 [MEAR-263] - Wrong docs in examples/customize-file-name-mapping.html
add 1c32f19 Fixed URL in link to Git repo.
add 2568cd3 [MEAR-260] - Remove finalName as a parameter
add 032dfa3 [MEAR-259] - Fix formatting date issues in apt files
new fdb22b6 [MEAR-263] - Wrong docs in examples/customize-file-name-mapping.html
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1523046)
\
N -- N -- N refs/heads/MEAR-263 (fdb22b6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
src/main/java/org/apache/maven/plugins/ear/EarMojo.java | 2 +-
src/site/apt/examples/customize-file-name-mapping.apt.vm | 2 +-
src/site/apt/examples/customizing-a-module-filename.apt.vm | 2 +-
src/site/apt/examples/customizing-context-root.apt.vm | 2 +-
src/site/apt/examples/customizing-module-uri.apt.vm | 2 +-
src/site/apt/examples/eclipse-and-maven-integration.apt.vm | 4 ++--
src/site/apt/examples/excluding-a-module.apt.vm | 2 +-
src/site/apt/examples/filtering-advanced.apt.vm | 2 +-
src/site/apt/examples/filtering-sources.apt.vm | 2 +-
src/site/apt/examples/generating-jboss-app.apt.vm | 2 +-
src/site/apt/examples/generating-modules-id.apt.vm | 2 +-
.../including-a-third-party-library-in-application-xml.apt.vm | 2 +-
.../specifying-env-entries-for-the-generated-application-xml.apt.vm | 2 +-
...ying-resource-ref-entries-for-the-generated-application-xml.apt.vm | 2 +-
...specifying-security-roles-for-the-generated-application-xml.apt.vm | 2 +-
src/site/apt/examples/unpacking-a-module.apt.vm | 2 +-
src/site/apt/examples/using-app-client.apt.vm | 2 +-
src/site/apt/modules.apt.vm | 2 +-
src/site/apt/tests.apt | 4 ++--
19 files changed, 21 insertions(+), 21 deletions(-)
--
To stop receiving notification emails like this one, please contact
khmarbaise@apache.org.
[maven-ear-plugin] 01/01: [MEAR-263] - Wrong docs in
examples/customize-file-name-mapping.html
Posted by kh...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a commit to branch MEAR-263
in repository https://gitbox.apache.org/repos/asf/maven-ear-plugin.git
commit fdb22b61e9229fa67f169ecfeb4127fc722fa928
Author: Karl Heinz Marbaise <kh...@apache.org>
AuthorDate: Thu Mar 8 21:20:23 2018 +0100
[MEAR-263] - Wrong docs in examples/customize-file-name-mapping.html
---
.../examples/customize-file-name-mapping.apt.vm | 38 +++++++++++++++++++---
1 file changed, 33 insertions(+), 5 deletions(-)
diff --git a/src/site/apt/examples/customize-file-name-mapping.apt.vm b/src/site/apt/examples/customize-file-name-mapping.apt.vm
index ea5a227..3b7e79a 100644
--- a/src/site/apt/examples/customize-file-name-mapping.apt.vm
+++ b/src/site/apt/examples/customize-file-name-mapping.apt.vm
@@ -3,6 +3,7 @@
------
Stephane Nicoll
<sn...@apache.org>
+ Karl Heinz Marbaise <kh...@apache.org>
------
2006-11-19
@@ -26,8 +27,14 @@
Customizing The File Name Mapping
- It might happen that your project has the same artifactId for different groups. To avoid file name
- clashing, specify the <<<full>>> file name mapping.
+
+ @Parameter( defaultValue = "@{groupId}@-@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@", required = true )
+ private String outputFileNameMapping;
+
+
+ It might happen that you need to change the naming of the artifacts within the EAR file.
+ This can be achieved by using the <<<outputFileNameMapping>>>. The following shows how it could be
+ configured in your pom file. In this example the default value is given as a starting point.
+--------
<build>
@@ -38,12 +45,33 @@ Customizing The File Name Mapping
<version>${project.version}</version>
<configuration>
[...]
- <fileNameMapping>full</fileNameMapping>
+ <outputFileNameMapping>@{groupId}@-@{artifactId}@-@{version}@@{dashClassifier?}@.@{extension}@</outputFileNameMapping>
</configuration>
</plugin>
</plugins>
</build>
+---------
- As a result, each artifact file name will be prefixed by the groupId to avoid clashes. There is also a
- <<<no-version>>> file name mapping if you do not want to get the version in the file names.
+ Based on the given things you can influence the resulting naming based on your wishes. For example you
+ want to have all artifacts within your ear file without a version you can change the configuration like the
+ following:
+
++--------
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-ear-plugin</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ [...]
+ <outputFileNameMapping>@{groupId}@-@{artifactId}@@{dashClassifier?}@.@{extension}@</outputFileNameMapping>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
++---------
+
+ Just a some words about the <<<@{dashClassifier?}@>>> which expands to a classifier including the preceding
+ dash which is needed to separate it from other parts of the artifact.
+
\ No newline at end of file
--
To stop receiving notification emails like this one, please contact
khmarbaise@apache.org.