52N/A<?
xml version="1.0" encoding="iso-8859-1"?>
52N/A DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. 695N/A Copyright (c) 1997-2015 Oracle and/or its affiliates. All rights reserved. 52N/A The contents of this file are subject to the terms of either the GNU 52N/A General Public License Version 2 only ("GPL") or the Common Development 52N/A and Distribution License("CDDL") (collectively, the "License"). You 292N/A may not use this file except in compliance with the License. You can 292N/A obtain a copy of the License at 52N/A language governing permissions and limitations under the License. 52N/A When distributing the software, include this License Header Notice in each 292N/A GPL Classpath Exception: 292N/A Oracle designates this particular file as subject to the "Classpath" 292N/A exception as provided by Oracle in the GPL Version 2 section of the License 292N/A file that accompanied this code. 292N/A If applicable, add the following below the License Header, with the fields 292N/A enclosed by brackets [] replaced by your own identifying information: 292N/A "Portions Copyright [year] [name of copyright owner]" 52N/A If you wish your version of this file to be governed by only the CDDL or 52N/A only the GPL Version 2, indicate your decision by adding "[Contributor] 52N/A elects to include this software in this distribution under the [CDDL or GPL 52N/A Version 2] license." If you don't indicate a single choice of license, a 52N/A recipient has the option to distribute your version of this file under 52N/A either the CDDL, the GPL Version 2 or to extend the choice of license to 52N/A its licensees as provided above. However, if you add GPL Version 2 code 52N/A and therefore, elected the GPL Version 2 license, then the option applies 52N/A only if the new code is made subject to such option by the copyright 377N/A <
artifactId>jvnet-parent</
artifactId>
6N/A <
modelVersion>4.0.0</
modelVersion>
6N/A <
artifactId>all</
artifactId>
6N/A <
packaging>pom</
packaging>
813N/A <
version>1.5.6-SNAPSHOT</
version>
6N/A <
name>JavaMail API distribution</
name>
377N/A <
system>Bugzilla</
system>
467N/A <
distribution>repo</
distribution>
549N/A <
comments>CDDL or GPL version 2 plus the Classpath Exception</
comments>
15N/A <!-- defaults that are overridden in mail module --> 194N/A <!-- for the osgiversion-maven-plugin --> 467N/A <
name>Bill Shannon</
name>
451N/A <
email>bill.shannon@oracle.com</
email>
467N/A <
organization>Oracle</
organization>
583N/A <!-- following to enable use of "mvn site:stage" --> 583N/A <
distributionManagement>
583N/A <
url>file:/tmp</
url>
<!-- not used --> 583N/A </
distributionManagement>
6N/A <
module>mail</
module>
6N/A <
module>mailapi</
module>
302N/A <
module>mailapijar</
module>
6N/A <
module>smtp</
module>
6N/A <
module>imap</
module>
6N/A <
module>pop3</
module>
6N/A <
module>dsn</
module>
695N/A <
module>mailhandler</
module>
754N/A <
module>android</
module>
63N/A This profile contains modules that should only be built 63N/A but not installed or deployed. 63N/A <
id>build-only</
id>
63N/A <
module>mbox</
module>
63N/A <
module>demo</
module>
63N/A <
module>client</
module>
63N/A <
module>servlet</
module>
63N/A <
module>webapp</
module>
63N/A <
module>taglib</
module>
168N/A <
module>logging</
module>
275N/A <
module>outlook</
module>
63N/A <
module>javadoc</
module>
552N/A <
module>publish</
module>
63N/A <
activeByDefault>true</
activeByDefault>
377N/A This profile is used for deploying a JavaMail final release. 63N/A Activating this profile manually for deployment causes 63N/A the above profile to be deactivated, which works around 63N/A an apparent bug in maven that prevents me from manually 63N/A deactivating a profile. This profile purposely has none 63N/A of the modules I don't want to be deployed. 377N/A <
id>deploy-release</
id>
288N/A <
module>parent-distrib</
module>
327N/A <
artifactId>maven-surefire-plugin</
artifactId>
377N/A <
artifactId>maven-javadoc-plugin</
artifactId>
377N/A <
id>attach-javadocs</
id>
377N/A <
artifactId>maven-gpg-plugin</
artifactId>
377N/A <
id>sign-artifacts</
id>
377N/A This profile is used for deploying a JavaMail SNAPSHOT release. 377N/A It's identical to the above deploy-release profile except that 377N/A artifacts aren't signed. 377N/A <
id>deploy-snapshot</
id>
377N/A <
module>parent-distrib</
module>
377N/A <
artifactId>maven-surefire-plugin</
artifactId>
377N/A <
artifactId>maven-javadoc-plugin</
artifactId>
377N/A <
id>attach-javadocs</
id>
487N/A A special profile for compiling with the real JDK 1.5 220N/A compiler, to make sure there are no accidental dependencies 220N/A <
artifactId>maven-compiler-plugin</
artifactId>
220N/A <
id>default-compile</
id>
515N/A <
compilerVersion>1.5</
compilerVersion>
793N/A <
arg>-Xlint:-finally</
arg>
789N/A <
showDeprecation>true</
showDeprecation>
789N/A <
showWarnings>true</
showWarnings>
26N/A <
defaultGoal>install</
defaultGoal>
565N/A Make sure we're using the correct version of maven. 213N/A <
artifactId>maven-enforcer-plugin</
artifactId>
222N/A <
id>enforce-version</
id>
222N/A <
version>[2.2.1,)</
version>
44N/A This plugin is reponsible for packaging artifacts 44N/A as OSGi bundles. Please refer to 44N/A for more information about how to use this plugin. 44N/A <
artifactId>maven-bundle-plugin</
artifactId>
206N/A <
DynamicImport-
Package>
206N/A </
DynamicImport-
Package>
44N/A Since we don't change the packaging type to bundle, we 44N/A need to configure the plugin to execute the manifest goal 44N/A during the process-classes phase of the build life cycle. 44N/A <
id>osgi-manifest</
id>
44N/A <
phase>process-classes</
phase>
44N/A <
goal>manifest</
goal>
194N/A Since we don't want a qualifier like b05 or SNAPSHOT to 194N/A appear in the OSGi package version attribute, we use 194N/A the following plugin to populate a project property 194N/A with an OSGi version that is equivalent to the maven 194N/A version without the qualifier. 194N/A <
artifactId>osgiversion-maven-plugin</
artifactId>
194N/A <
dropVersionComponent>qualifier</
dropVersionComponent>
194N/A <
id>compute-osgi-version</
id>
194N/A <
goal>compute-osgi-version</
goal>
487N/A Use the 1.5 compiler for JavaMail itself and the test classes. 467N/A <
artifactId>maven-compiler-plugin</
artifactId>
213N/A <
id>default-compile</
id>
800N/A XXX - workaround for bug in maven compiler 800N/A plugin versions 3.0 - 3.3 (at least): 800N/A <
useIncrementalCompilation>false</
useIncrementalCompilation>
213N/A <
id>default-testCompile</
id>
15N/A <
artifactId>maven-jar-plugin</
artifactId>
44N/A Configure the maven-jar-plugin to pick up 44N/A the maven-bundle-plugin. 15N/A <
Specification-
Title>
15N/A </
Specification-
Title>
15N/A <
Specification-
Version>
302N/A </
Specification-
Version>
15N/A <
Specification-
Vendor>
15N/A </
Specification-
Vendor>
15N/A <
Implementation-
Title>
15N/A </
Implementation-
Title>
15N/A <
Implementation-
Version>
15N/A </
Implementation-
Version>
15N/A <
Implementation-
Vendor>
15N/A </
Implementation-
Vendor>
15N/A <
Implementation-
Vendor-
Id>
15N/A </
Implementation-
Vendor-
Id>
190N/A <
Probe-
Provider-
XML-
File-
Names>
190N/A </
Probe-
Provider-
XML-
File-
Names>
15N/A <
exclude>**/*.java</
exclude>
372N/A Tell the source plugin about the sources that may have 372N/A been downloaded by the maven-dependency-plugin. 467N/A that's copied there will also be compiled when using 467N/A the latest version of the maven-compiler-plugin. 372N/A <
artifactId>build-helper-maven-plugin</
artifactId>
467N/A <
phase>generate-sources</
phase>
372N/A <
goal>add-source</
goal>
467N/A <
source>
<!-- for dependencies --> 372N/A Configure the source plugin here so that it will know 372N/A about the sources that may have been downloaded by the 372N/A maven-dependency-plugin and configured by the 372N/A build-helper-maven-plugin. 372N/A <
artifactId>maven-source-plugin</
artifactId>
372N/A <
id>attach-sources</
id>
372N/A <
goal>jar-no-fork</
goal>
372N/A <
includePom>true</
includePom>
467N/A Since we added the classes directory using the 467N/A build-helper-maven-plugin above, we need to exclude 467N/A the class files from the source jar file. 467N/A <
exclude>**/*.class</
exclude>
63N/A <artifactId>maven-release-plugin</artifactId> 63N/A <arguments>-P deploy</arguments> 441N/A <
artifactId>maven-compiler-plugin</
artifactId>
441N/A <
artifactId>maven-surefire-plugin</
artifactId>
441N/A <
version>2.4.3</
version>
441N/A <
artifactId>maven-jar-plugin</
artifactId>
761N/A <!-- need at least this version to make excludes work --> 441N/A <
artifactId>build-helper-maven-plugin</
artifactId>
549N/A <
artifactId>maven-assembly-plugin</
artifactId>
164N/A By default, disable the FindBugs plugin for all modules. 367N/A It's enabled in the modules where we actually want to 164N/A <
artifactId>findbugs-maven-plugin</
artifactId>
367N/A <
findbugsXmlWithMessages>true</
findbugsXmlWithMessages>
314N/A <
artifactId>maven-enforcer-plugin</
artifactId>
314N/A <
artifactId>maven-bundle-plugin</
artifactId>
314N/A <
version>2.1.0</
version>
371N/A <
artifactId>maven-source-plugin</
artifactId>
371N/A <
version>2.1.2</
version>
457N/A <
artifactId>maven-javadoc-plugin</
artifactId>
721N/A <
version>2.10</
version>
721N/A <!-- make all the APIs available for javadoc --> 721N/A <
additionalDependencies>
721N/A </
additionalDependency>
745N/A <
artifactId>gimap</
artifactId>
745N/A </
additionalDependency>
721N/A </
additionalDependencies>
457N/A <
artifactId>maven-war-plugin</
artifactId>
583N/A <
artifactId>maven-project-info-reports-plugin</
artifactId>
32N/A <
dependencyManagement>
32N/A <
artifactId>dsn</
artifactId>
459N/A <
artifactId>gimap</
artifactId>
32N/A <
artifactId>mbox</
artifactId>
32N/A <
artifactId>taglib</
artifactId>
32N/A <
artifactId>servlet-api</
artifactId>
32N/A <
version>2.5</
version>
32N/A <
artifactId>jsp-api</
artifactId>
32N/A <
version>2.1</
version>
32N/A </
dependencyManagement>
367N/A Configure FindBugs to run with "mvn site" and 367N/A generate html output that can be viewed directly. 367N/A <
artifactId>findbugs-maven-plugin</
artifactId>