icefaces-compat
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>org.icefaces</groupId>
<artifactId>icefaces-compat</artifactId>
<version>3.3.0</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<!--
~ Copyright 2004-2013 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>
<parent>
<groupId>org.icefaces</groupId>
<artifactId>bundle-parent</artifactId>
<version>3.3.0</version>
<relativePath>..</relativePath>
</parent>
<artifactId>${icefaces.lib.name}-compat</artifactId>
<packaging>pom</packaging>
<name>${icefaces.product.name} Compat Components</name>
<url>http://www.icesoft.org</url>
<description>${icefaces.product.name} Compat Component Library</description>
<build>
<plugins>
<!-- Not quite fully Maven yet so some Ant is required. -->
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<!-- Run the default Ant build to clean everything -->
<execution>
<id>clean-all</id>
<phase>clean</phase>
<configuration>
<target>
<ant antfile="./build.xml" target="clean"/>
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
<!-- Run the default Ant build to build everything -->
<execution>
<id>compile-all</id>
<phase>compile</phase>
<configuration>
<target>
<ant antfile="./build.xml"/>
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
<!-- Generate JavaDoc files using Ant during "package" phase -->
<execution>
<id>gen-javadocs</id>
<phase>verify</phase>
<configuration>
<target>
<ant dir="./core" antfile="build.xml" target="javadoc"/>
</target>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.apache.ant</groupId>
<artifactId>ant-junit</artifactId>
<version>1.8.2</version>
</dependency>
</dependencies>
</plugin>
<!-- The following two plugins are the way that are supposed to be used to
add source directories for creating the sources jar file but it doesn't
seem to work. So instead we use the assembly method until we can
re-arrange the layout to better suit Maven conventions. -->
<!-- This plugin allows us to have more than a single path to the source
files as we are dealing with code from both component and core. -->
<!--<plugin>-->
<!--<groupId>org.codehaus.mojo</groupId>-->
<!--<artifactId>build-helper-maven-plugin</artifactId>-->
<!--<version>1.7</version>-->
<!--<executions>-->
<!--<execution>-->
<!--<id>add-source</id>-->
<!--<phase>generate-sources</phase>-->
<!--<goals>-->
<!--<goal>add-source</goal>-->
<!--</goals>-->
<!--<configuration>-->
<!--<sources>-->
<!--<source>./components/src/main/java</source>-->
<!--<source>./core/src/main/java</source>-->
<!--</sources>-->
<!--</configuration>-->
<!--</execution>-->
<!--</executions>-->
<!--</plugin>-->
<!--<plugin>-->
<!--<groupId>org.apache.maven.plugins</groupId>-->
<!--<artifactId>maven-source-plugin</artifactId>-->
<!--<version>2.1.2</version>-->
<!--<executions>-->
<!--<execution>-->
<!--<id>attach-sources</id>-->
<!--<goals>-->
<!--<goal>jar-no-fork</goal>-->
<!--</goals>-->
<!--</execution>-->
<!--</executions>-->
<!--</plugin>-->
<!-- Since I couldn't get the above strategy to work for the source files, I used this
assembly approach instead. It basically merges the two source directories together
and jars them with the proper name. -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.3</version>
<configuration>
<descriptors>
<descriptor>assemble-sources.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>verify</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Builds the JavaDocs jar -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.4</version>
<executions>
<execution>
<id>attach-javadocs</id>
<phase>verify</phase>
<configuration>
<classifier>javadoc</classifier>
<classesDirectory>./core/build/javadocs</classesDirectory>
</configuration>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Since we still rely on Ant and pre-built jars, we use this plugin to simply add
the jar in as an artifact and it gets injected into the build phases for normal
installation and deployment. -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>attach-artifacts</id>
<phase>package</phase>
<goals>
<goal>attach-artifact</goal>
</goals>
<configuration>
<artifacts>
<artifact>
<file>./core/build/dist/${icefaces.lib.name}-compat.jar</file>
<type>jar</type>
</artifact>
</artifacts>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>${icefaces.product.group}</groupId>
<artifactId>${icefaces.lib.name}</artifactId>
</dependency>
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
<version>1.8.0</version>
<exclusions>
<exclusion>
<artifactId>commons-logging</artifactId>
<groupId>commons-logging</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1</version>
<exclusions>
<exclusion>
<artifactId>servlet-api</artifactId>
<groupId>javax.servlet</groupId>
</exclusion>
<exclusion>
<artifactId>log4j</artifactId>
<groupId>log4j</groupId>
</exclusion>
<exclusion>
<artifactId>logkit</artifactId>
<groupId>logkit</groupId>
</exclusion>
<exclusion>
<artifactId>avalon-framework</artifactId>
<groupId>avalon-framework</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>javax.el</groupId>
<artifactId>el-api</artifactId>
</dependency>
<!-- Required for panelSeries at run time. -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>jstl</artifactId>
<version>1.2</version>
</dependency>
<!-- Required if using dataExporter component -->
<!--<dependency>-->
<!--<groupId>net.sourceforge.jexcelapi</groupId>-->
<!--<artifactId>jxl</artifactId>-->
<!--<version>2.6.8</version>-->
<!--</dependency>-->
<!-- Required if using Krysalis jcharts -->
<!--<dependency>-->
<!--<groupId>net.sf.jcharts</groupId>-->
<!--<artifactId>krysalis-jCharts</artifactId>-->
<!--<version>1.0.0-alpha-1</version>-->
<!--</dependency>-->
</dependencies>
<profiles>
<!-- Not sure why but when I tried to put this in the top-level parent pom, it would sign all the artifacts
but would only deploy the signatures for the main .jar and not the the sources and javadoc jars. It
apparently works fine if the profile is defined in each project so that's what I've done for now. -->
<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.4</version>
<executions>
<execution>
<id>sign-library</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
<configuration>
<keyname>${icefaces.gpg.keyname}</keyname>
<passphrase>${icefaces.gpg.passphrase}</passphrase>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</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