bundle-parent
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>org.icefaces</groupId>
<artifactId>bundle-parent</artifactId>
<version>4.3.0</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<!--
~ Copyright 2004-2018 ICEsoft Technologies Canada Corp.
~
~ Licensed 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.
-->
<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>
<groupId>org.icefaces</groupId>
<!-- <groupId>com.icesoft.icefaces-ee</groupId> -->
<artifactId>bundle-parent</artifactId>
<version>4.3.0</version>
<packaging>pom</packaging>
<name>ICEfaces</name>
<description>ICEfaces Parent Project</description>
<!-- <name>ICEfaces EE</name>
<description>ICEfaces EE Parent Project</description> -->
<url>http://www.icesoft.org</url>
<licenses>
<license>
<name>Apache License Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<name>ICEsoft Technologies Canada Corp.</name>
<email>product.support@icesoft.com</email>
</developer>
</developers>
<distributionManagement>
<!-- By default, SNAPSHOT and releases are deployed to the local filesystem for
verification and inspection. To deploy SNAPSHOTS and releases to the
remote repositories, specify -DdeployRemote="true" which will trigger the
appropriate profile (see below). -->
<snapshotRepository>
<id>icefaces-local-snapshot</id>
<name>Local filesystem repository for testing</name>
<url>file://${user.home}/icefaces/local-test-repo/snapshots</url>
</snapshotRepository>
<repository>
<id>icefaces-local-release</id>
<name>Local filesystem repository for testing</name>
<url>file://${user.home}/icefaces/local-test-repo/releases</url>
</repository>
</distributionManagement>
<scm>
<connection>scm:svn:http://anonsvn.icesoft.org/repo/icefaces4/trunk/icefaces</connection>
<developerConnection>scm:svn:http://anonsvn.icesoft.org/repo/icefaces4/trunk/icefaces</developerConnection>
<url>http://anonsvn.icesoft.org/repo/icefaces4/</url>
<tag>HEAD</tag>
</scm>
<modules>
<module>icepush</module>
<module>core</module>
<module>ace</module>
<module>mobi</module>
<module>samples</module>
<!-- Additional modules for EE-only -->
<!--
<module>ext</module>
<module>mobile-simulator</module>
-->
</modules>
<properties>
<maven.test.skip>true</maven.test.skip>
<!-- Properties for specifying the product being used (open source) -->
<icefaces.product.group>org.icefaces</icefaces.product.group>
<icefaces.product.name>ICEfaces</icefaces.product.name>
<icefaces.lib.name>icefaces</icefaces.lib.name>
<icepush.product.group>org.icepush</icepush.product.group>
<icepush.product.name>ICEpush</icepush.product.name>
<icepush.lib.name>icepush</icepush.lib.name>
<!-- Properties for specifying the product being used (EE) -->
<!--
<icefaces.product.group>com.icesoft.icefaces-ee</icefaces.product.group>
<icefaces.product.name>ICEfaces EE</icefaces.product.name>
<icefaces.lib.name>icefaces-ee</icefaces.lib.name>
<icepush.product.group>com.icesoft.icepush-ee</icepush.product.group>
<icepush.product.name>ICEpush EE</icepush.product.name>
<icepush.lib.name>icepush-ee</icepush.lib.name>
-->
<icesoft.company.name>ICEsoft Technologies Inc.</icesoft.company.name>
<icesoft.copyright>ICEsoft Technologies Canada Corp., All Rights Reserved.</icesoft.copyright>
<icesoft.copyright.year>2018</icesoft.copyright.year>
<javadoc.title>
${icefaces.product.name} Java API Documentation
</javadoc.title>
<javadoc.header>
${icefaces.product.name} ${project.version}<br>Java API Documentation
</javadoc.header>
<tld.title>
${icefaces.product.name} ${project.version} Tag Library Reference
</tld.title>
<!-- Versions of JSF implementations -->
<mojarra.version>2.3.5</mojarra.version>
<myfaces.version>2.3.1</myfaces.version>
<!-- Various library versions settable from one place -->
<annotation.version>1.0</annotation.version>
<el.version>2.2.1</el.version>
<el.compat.version>1.0</el.compat.version>
<portlet.api.version>2.0</portlet.api.version>
<servlet.api.version>3.0.1</servlet.api.version>
<!-- Use with Liferay 6.2 -->
<liferayfaces.version>4.2.5-ga6</liferayfaces.version>
<!-- Use with Apache Pluto -->
<pluto.version>2.0.2</pluto.version>
<!-- To avoid warnings about platform dependent actions when copying resources -->
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.3</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.7</version>
<dependencies>
<dependency>
<groupId>com.google.code.maven-svn-wagon</groupId>
<artifactId>maven-svn-wagon</artifactId>
<version>1.4</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.1</version>
</plugin>
</plugins>
</build>
<repositories>
<repository>
<id>sonatype.snapshots</id>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
<repository>
<id>java.net</id>
<url>http://download.java.net/maven/2</url>
</repository>
<repository>
<id>maven.org</id>
<url>http://repo1.maven.org/maven2</url>
</repository>
<repository>
<id>jvnet-nexus-releases</id>
<name>jvnet-nexus-releases</name>
<url>https://maven.java.net/content/repositories/releases</url>
</repository>
<repository>
<id>jvnet-nexus-snapshots</id>
<name>jvnet-nexus-snapshots</name>
<url>https://maven.java.net/content/repositories/snapshots/</url>
</repository>
<repository>
<id>releases</id>
<url>http://anonsvn.icefaces.org/repo/maven2/releases</url>
</repository>
<repository>
<id>snapshots</id>
<url>http://anonsvn.icefaces.org/repo/maven2/snapshots</url>
</repository>
<repository>
<id>apache.org</id>
<url>https://repository.apache.org</url>
</repository>
<repository>
<id>liferay.previews</id>
<url>https://repository.liferay.com/nexus/content/repositories/liferay-previews</url>
</repository>
</repositories>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.glassfish</groupId>
<artifactId>javax.faces</artifactId>
<version>${mojarra.version}</version>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>${servlet.api.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.portlet</groupId>
<artifactId>portlet-api</artifactId>
<version>${portlet.api.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.el</groupId>
<artifactId>javax.el-api</artifactId>
<version>${el.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.el</groupId>
<artifactId>el-api</artifactId>
<version>${el.compat.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}</artifactId>
<version>${project.version}</version>
<exclusions>
<exclusion>
<groupId>org.glassfish</groupId>
<artifactId>javax.faces</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- ICEfaces EE Only -->
<!--
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}-ext</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}-mobile-simulator</artifactId>
<version>${project.version}</version>
</dependency>
-->
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}-ace</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}-mobi</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${icepush.product.group}</groupId>
<artifactId>${icepush.lib.name}</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>javax.annotation</groupId>
<artifactId>jsr250-api</artifactId>
<version>${annotation.version}</version>
<scope>provided</scope>
</dependency>
<!-- Dependencies for EE-only -->
<!--
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}-ext</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}-mobile-simulator</artifactId>
<version>${project.version}</version>
</dependency>
-->
</dependencies>
</dependencyManagement>
<!-- There is a bug (http://jira.codehaus.org/browse/MANTRUN-20) that occurs
when Maven uses the antrun plugin that results in JAVA_HOME pointing to
the JRE directory rather than the JDK. -->
<profiles>
<profile>
<id>tools.jar</id>
<activation>
<file>
<exists>${java.home}/../lib/tools.jar</exists>
</file>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.6.0</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>sign-artifacts</id>
<activation>
<!--<activeByDefault>true</activeByDefault>-->
<property>
<name>signArtifacts</name>
</property>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.6</version>
<executions>
<execution>
<id>sign-library</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
<configuration>
<keyname>${gpg.keyname}</keyname>
<passphraseServerId>${gpg.keyname}</passphraseServerId>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>deployRemote</id>
<activation>
<property>
<name>deployRemote</name>
<value>true</value>
</property>
</activation>
<distributionManagement>
<!-- SNAPSHOT releases currently go to our own svn repository but if we can
switch to Sonatype by changing to the entry commented out below. -->
<snapshotRepository>
<id>icefaces-remote</id>
<name>ICEsoft Maven Repository</name>
<url>svn:http://dev.icesoft.com/svn/ossrepo/maven2/snapshots/</url>
</snapshotRepository>
<!--<snapshotRepository>-->
<!--<id>sonatype-nexus-snapshots</id>-->
<!--<name>Sonatype Nexus Snapshots</name>-->
<!--<url>https://oss.sonatype.org/content/repositories/snapshots/</url>-->
<!--</snapshotRepository>-->
<!-- Uncomment this repo to publish to the public Sonatype staging repo -->
<repository>
<id>sonatype-nexus-staging</id>
<name>Nexus Release Repository</name>
<url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>
</repository>
<!-- Uncomment this repo to publish to the public ICEsoft maven releases repo -->
<!-- <repository>
<id>icefaces-releases-repository</id>
<name>ICEfaces Releases Repository</name>
<url>svn:http://dev.icesoft.com/svn/ossrepo/maven2/releases/</url>
</repository> -->
</distributionManagement>
</profile>
</profiles>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report