<?xml version="1.0" encoding="UTF-8"?>
<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>
        <groupId>org.mule</groupId>
        <artifactId>mule</artifactId>
        <version>2.0.1</version>
    </parent>
    <groupId>org.mule.transports</groupId>
    <artifactId>mule-transports</artifactId>
    <packaging>pom</packaging>
    <name>Mule Transports</name>

    <dependencies>
        <dependency>
            <groupId>org.mule</groupId>
            <artifactId>mule-core</artifactId>
            <version>${version}</version>
        </dependency>
        <dependency>
            <groupId>org.mule.modules</groupId>
            <artifactId>mule-module-spring-config</artifactId>
            <version>${version}</version>
            <scope>provided</scope>
        </dependency>
        <!-- Now that m2 dependency resolution works, activation
             should ONLY come via core or (in the future) core-api, but there is
             OF COURSE a bug with m2's handling of provided dependencies:
             http://jira.codehaus.org/browse/MNG-2205
        -->
        <dependency>
            <groupId>javax.activation</groupId>
            <artifactId>activation</artifactId>
            <scope>provided</scope>
        </dependency>

        <dependency>
            <groupId>org.mule.tests</groupId>
            <artifactId>mule-tests-functional</artifactId>
            <version>${version}</version>
            <scope>test</scope>
        </dependency>

    </dependencies>

    <profiles>
        <profile>
            <id>osgi</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.apache.felix</groupId>
                        <artifactId>maven-bundle-plugin</artifactId>
                        <configuration>
                            <instructions>
                                <Bundle-Category>Mule Transport</Bundle-Category>
                                <Bundle-Activator>org.mule.module.osgi.TransportActivator</Bundle-Activator>
                                <!-- The Bundle-Activator can't be imported from another bundle,
                                    so we need to have a local copy of it. -->
                                <Private-Package>
                                    org.mule.module.osgi
                                </Private-Package>
                                <!-- Since org.mule.module.osgi is included as a private package,
                                    we need to explicitly declare its imports (they aren't
                                    automatically generated.
                                    Note: manifest settings don't get merged with the parent, so
                                    we need to repeat all settings from ../pom.xml here :-( -->
                                <Import-Package>
                                    org.mule.providers.service,
                                    !com.ccg.net.ethernet,
                                    !com.sun.activation.registries,
                                    !com.sun.net.ssl,
                                    !com.sun.net.ssl.internal.ssl,
                                    !javax.crypto,
                                    !javax.crypto.spec,
                                    !javax.naming,
                                    !javax.naming.spi,
                                    !javax.net,
                                    !javax.net.ssl,
                                    !javax.security.auth,
                                    !javax.security.cert,
                                    !javax.xml.namespace,
                                    !javax.xml.transform,
                                    !org.xml.sax,
                                    !sun.misc,
                                    *
                                </Import-Package>
                            </instructions>
                        </configuration>
                    </plugin>
                 </plugins>
            </build>
        </profile>
        <profile>
            <id>jdk14</id>
            <activation>
                <property>
                    <!--
                        This profile is always active and is NOT activated by JDK
                        on purpose. We always want to compile at least the 1.4 compatible
                        sources as the bottom line.

                        To disable this profile specify -DskipJDK14=true on the commandline
                        -->
                    <name>!skipJDK14</name>
                </property>
            </activation>
            <modules>
                <module>all-transports</module>
                <module>axis</module>
                <module>bpm</module>
                <module>ejb</module>
                <module>email</module>
                <module>file</module>
                <module>ftp</module>
                <module>http</module>
                <module>jbpm</module>
                <module>jdbc</module>
                <module>jms</module>
                <module>multicast</module>
                <module>quartz</module>
                <module>rmi</module>
                <module>soap</module>
                <module>ssl</module>
                <module>stdio</module>
                <module>tcp</module>
                <module>udp</module>
                <module>vm</module>
                <module>xmpp</module>
            </modules>
        </profile>
        <profile>
            <id>jdk15</id>
            <activation>
                <jdk>1.5</jdk>
            </activation>
            <modules>
                <module>cxf</module>
            </modules>
        </profile>
    </profiles>
</project>
