52N/A<?
xml version="1.0" encoding="iso-8859-1"?>
292N/A DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. 52N/A Copyright 1997-2009 Sun Microsystems, Inc. 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 52N/A may not use this file except in compliance with the License. You can obtain 292N/A language governing permissions and limitations under the License. 52N/A When distributing the software, include this License Header Notice in each 52N/A Sun designates this particular file as subject to the "Classpath" exception 292N/A as provided by Sun in the GPL Version 2 section of the License file that 292N/A accompanied this code. If applicable, add the following below the License 292N/A Header, with the fields enclosed by brackets [] replaced by your own 292N/A identifying information: "Portions Copyrighted [year] 292N/A [name of copyright owner]" 292N/A If you wish your version of this file to be governed by only the CDDL or 292N/A only the GPL Version 2, indicate your decision by adding "[Contributor] 292N/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 52N/A <
modelVersion>4.0.0</
modelVersion>
6N/A <
artifactId>all</
artifactId>
6N/A <
packaging>pom</
packaging>
6N/A <
version>1.4.3-SNAPSHOT</
version>
6N/A <
name>JavaMail API distribution</
name>
302N/A <
distribution>repo</
distribution>
6N/A <
comments>A business-friendly OSS license</
comments>
6N/A <
name>GPLv2+CE</
name>
6N/A <
distribution>repo</
distribution>
6N/A <
comments>GPL version 2 plus the Classpath Exception</
comments>
6N/A <
name>Sun Microsystems, Inc.</
name>
6N/A <!-- defaults that are overridden in mail module --> 44N/A <
name>Bill Shannon</
name>
191N/A <
organization>Sun Microsystems, Inc.</
organization>
44N/A <
module>mail</
module>
190N/A <
module>mailapi</
module>
367N/A This profile contains modules that should only be built 367N/A but not installed or deployed. 6N/A <
module>mbox</
module>
6N/A <
module>demo</
module>
6N/A <
module>client</
module>
6N/A <
module>servlet</
module>
6N/A <
module>webapp</
module>
6N/A <
module>taglib</
module>
302N/A <
module>javadoc</
module>
6N/A <
activeByDefault>true</
activeByDefault>
6N/A Activating this profile manually for deployment causes 6N/A the above profile to be deactivated, which works around 302N/A an apparent bug in maven that prevents me from manually 6N/A deactivating a profile. This profile purposely has none 6N/A of the modules I don't want to be deployed. 63N/A <
distributionManagement>
63N/A </
distributionManagement>
63N/A <
defaultGoal>install</
defaultGoal>
63N/A This plugin is reponsible for packaging artifacts 63N/A as OSGi bundles. Please refer to 275N/A for more information about how to use this plugin. 63N/A <
artifactId>maven-bundle-plugin</
artifactId>
63N/A Since we don't change the packaging type to bundle, we 288N/A need to configure the plugin to execute the manifest goal 288N/A during the process-classes phase of the build life cycle. 327N/A <
phase>process-classes</
phase>
63N/A <
artifactId>maven-compiler-plugin</
artifactId>
220N/A <
artifactId>maven-jar-plugin</
artifactId>
220N/A <!-- need at least this version to make excludes work --> 220N/A Configure the maven-jar-plugin to pick up 220N/A the maven-bundle-plugin. 220N/A <
Specification-
Version>
220N/A </
Specification-
Vendor>
220N/A </
Implementation-
Title>
220N/A <
Implementation-
Version>
220N/A </
Implementation-
Version>
220N/A <
Implementation-
Vendor>
63N/A </
Implementation-
Vendor>
63N/A <
Implementation-
Vendor-
Id>
63N/A </
Implementation-
Vendor-
Id>
187N/A <
exclude>**/*.java</
exclude>
6N/A This is the rule that creates the zip file for distribution. 213N/A <
artifactId>maven-assembly-plugin</
artifactId>
213N/A <
inherited>false</
inherited>
213N/A I'd like this to be run as part of the 213N/A package phase, but that doesn't work. 213N/A Have to run it explicitly as: 222N/A mvn package assembly:assembly 44N/A <artifactId>maven-release-plugin</artifactId> 44N/A <arguments>-P deploy</arguments> 191N/A By default, disable the FindBugs plugin for all modules. 191N/A It's enabled in the "mail" module, which is the only 44N/A module where we actually want to run it. 206N/A <
artifactId>findbugs-maven-plugin</
artifactId>
44N/A </
pluginManagement>
44N/A <
artifactId>wagon-svn</
artifactId>
44N/A Following should be: 44N/A <version>RELEASE</version> 44N/A but Kohsuke says it doesn't work and to replace 44N/A it with the actual version number. 44N/A <
version>1.8</
version>
194N/A <
artifactId>mail</
artifactId>
194N/A <
artifactId>dsn</
artifactId>
194N/A <
artifactId>mbox</
artifactId>
194N/A <
artifactId>taglib</
artifactId>
213N/A <
artifactId>servlet-api</
artifactId>
213N/A <
artifactId>jsp-api</
artifactId>
213N/A </
dependencyManagement>
213N/A <
artifactId>activation</
artifactId>
213N/A <!-- following works around a bug that causes NullPointerException --> 213N/A <
groupId>junit</
groupId>
213N/A <
artifactId>junit</
artifactId>
6N/A <
version>4.3.1</
version>