<!--
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
The contents of this file are subject to the terms of either the GNU
General Public License Version 2 only ("GPL") or the Common Development
and Distribution License("CDDL") (collectively, the "License"). You
may not use this file except in compliance with the License. You can
obtain a copy of the License at
or packager/legal/LICENSE.txt. See the License for the specific
language governing permissions and limitations under the License.
When distributing the software, include this License Header Notice in each
file and include the License file at packager/legal/LICENSE.txt.
GPL Classpath Exception:
Oracle designates this particular file as subject to the "Classpath"
exception as provided by Oracle in the GPL Version 2 section of the License
file that accompanied this code.
Modifications:
If applicable, add the following below the License Header, with the fields
enclosed by brackets [] replaced by your own identifying information:
"Portions Copyright [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the CDDL or
only the GPL Version 2, indicate your decision by adding "[Contributor]
elects to include this software in this distribution under the [CDDL or GPL
Version 2] license." If you don't indicate a single choice of license, a
recipient has the option to distribute your version of this file under
either the CDDL, the GPL Version 2 or to extend the choice of license to
its licensees as provided above. However, if you add GPL Version 2 code
and therefore, elected the GPL Version 2 license, then the option applies
only if the new code is made subject to such option by the copyright
holder.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<artifactId>webservices</artifactId>
<version>3.1.2</version>
</parent>
<artifactId>webservices-scripts</artifactId>
<name>GlassFish webservices scripts</name>
<!--
The comments below were copied from the appclient-scripts module.
They are very helpful so it seemed like a good idea to leave them here also.
-->
<!--
This packaging specifies that it's a package that contains files to be added to
the distribution.
In this packaging mode, the build will produce a jar, like it normally does for
the <packaging>jar</packaging>, but the contents of this jar is then extracted
when the final GlassFish distribution is assembled. (But when this happens,
META-INF/** in the jar will be ignored.)
For a fragment to be added to the distribution, the distribution POM needs
to directly or indirectly depend on the fragment module. This is normally
done by creating a feature-level grouping POM (which allows you to bundle multiple
modules and treat it as a single dependency - see the webtier-all module for example),
and have that declare a dependency on the fragment, instead of directly
modifying the distribution POM.
So the idea here is that individual technology area will create their own
fragments that contain pieces that they need, and when the said technology
is bundled in GF, the corresponding fragment will be also added, thanks to
the transitive dependency handling in Maven.
-->
<packaging>distribution-fragment</packaging>
<!--
<packaging>pom</packaging>
--> <build>
<!--
In this module, all the files are statically stored as-is in the Subversion repository,
is suffice.
But in more complex scenario, one can use maven-antrun-extended-plugin and use a series of Ant tasks
to perform processing on resources, such as token replacement, file generation, pre-processing, etc.
The following section shows how you can do this.
-->
<plugins>
<plugin>
<artifactId>maven-glassfishbuild-plugin</artifactId>
</plugin>
</plugins>
<extensions>
<extension>
<artifactId>maven-glassfishbuild-extension</artifactId>
</extension>
</extensions>
</build>
</project>