diff --git a/src/site/apt/examples/skinny-wars.apt.vm b/src/site/apt/examples/skinny-wars.apt.vm deleted file mode 100644 index f530dbdd..00000000 --- a/src/site/apt/examples/skinny-wars.apt.vm +++ /dev/null @@ -1,112 +0,0 @@ - ------ - Creating Skinny WARs - ------ - Mike Perham - Karl-Heinz Marbaise - ------ - 2014-10-01 - ------ - -~~ Licensed to the Apache Software Foundation (ASF) under one -~~ or more contributor license agreements. See the NOTICE file -~~ distributed with this work for additional information -~~ regarding copyright ownership. The ASF licenses this file -~~ to you under the Apache License, Version 2.0 (the -~~ "License"); you may not use this file except in compliance -~~ with the License. You may obtain a copy of the License at -~~ -~~ http://www.apache.org/licenses/LICENSE-2.0 -~~ -~~ Unless required by applicable law or agreed to in writing, -~~ software distributed under the License is distributed on an -~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY -~~ KIND, either express or implied. See the License for the -~~ specific language governing permissions and limitations -~~ under the License. - -~~ NOTE: For help with the syntax of this file, see: -~~ http://maven.apache.org/doxia/references/apt-format.html - -Creating Skinny WARs - - In a typical J2EE environment, a WAR is packaged within an EAR for deployment. The - WAR can contain all its dependent JARs in <<>> but then the EAR can quickly grow - very large if there are multiple WARs, due to the presence of duplicate JARs. Instead - the J2EE specification allows WARs to reference external JARs packaged within the EAR - via the <<>> setting in their <<>>. - - The Maven EAR Plugin has direct support for creating skinny wars which simply - means to {{{http://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html}configure the maven-ear-plugin}} - accordingly. - - You need to change the EAR project's <<>> to package those dependent JARs in the EAR. - Notice that we package everything into a <<>> directory within the EAR. This is - just my own personal preference to distinguish between J2EE modules (which will - be packaged in the root of the EAR) and Java libraries (which are packaged in <<>>). - -+-----------------+ - - ... - - - - maven-ear-plugin - 2.9.1 - - lib/ - true - - - - - ... - -+-----------------+ - - Now the painful part. Your EAR project's <<>> needs to list every dependency that the WAR has. - This is because Maven assumes fat WARs and does not include transitive dependencies - of WARs within the EAR. - -+-----------------+ - - .... - - - com.acme - shared-jar - 1.0.0 - - - com.acme - war1 - 1.0.0 - war - - - com.acme - war2 - 1.0.0 - war - - - ... - -+-----------------+ - - Your EAR will contain something like this: - ------------------ - . - |-- META-INF - | `-- application.xml - |-- lib - | `-- shared-jar-1.0.0.jar - |-- war1-1.0.0.war - `-- war2-1.0.0.war ------------------ - - -* Alternatives - - Our users have submitted alternatives to the above recipe on - {{{http://docs.codehaus.org/display/MAVENUSER/Solving+the+Skinny+Wars+problem}the Wiki}}. diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm index edcc5c5c..466baccf 100644 --- a/src/site/apt/index.apt.vm +++ b/src/site/apt/index.apt.vm @@ -83,7 +83,7 @@ ${project.name} * {{{./examples/rapid-testing-jetty6-plugin.html}Rapid Testing the Jetty Plugin}} - * {{{./examples/skinny-wars.html}Creating Skinny WARs}} + * {{{https://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html}Creating Skinny WARs}} * {{{./examples/including-excluding-files-from-war.html}Including and Excluding Files From the WAR}} diff --git a/src/site/site.xml b/src/site/site.xml index 2f81f26c..98febf37 100644 --- a/src/site/site.xml +++ b/src/site/site.xml @@ -40,7 +40,7 @@ under the License. - +