Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
<?xml version="1.0" encoding="UTF-8"?>
<!--
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright (c) 1997-2017 Oracle and/or its affiliates. All rights reserved.
The contents of this file are subject to the terms of either the GNU
General Public License Version 2 only ("GPL") or the Common Development
and Distribution License("CDDL") (collectively, the "License"). You
may not use this file except in compliance with the License. You can
obtain a copy of the License at
https://oss.oracle.com/licenses/CDDL+GPL-1.1
or LICENSE.txt. See the License for the specific
language governing permissions and limitations under the License.
When distributing the software, include this License Header Notice in each
file and include the License file at LICENSE.txt.
GPL Classpath Exception:
Oracle designates this particular file as subject to the "Classpath"
exception as provided by Oracle in the GPL Version 2 section of the License
file that accompanied this code.
Modifications:
If applicable, add the following below the License Header, with the fields
enclosed by brackets [] replaced by your own identifying information:
"Portions Copyright [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the CDDL or
only the GPL Version 2, indicate your decision by adding "[Contributor]
elects to include this software in this distribution under the [CDDL or GPL
Version 2] license." If you don't indicate a single choice of license, a
recipient has the option to distribute your version of this file under
either the CDDL, the GPL Version 2 or to extend the choice of license to
its licensees as provided above. However, if you add GPL Version 2 code
and therefore, elected the GPL Version 2 license, then the option applies
only if the new code is made subject to such option by the copyright
holder.
-->
<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">
<parent>
<groupId>org.glassfish.main.external</groupId>
<artifactId>nucleus-external</artifactId>
<version>5.0</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>bean-validator</artifactId>
<name>javax.validation:${javax.validation.version} as OSGi bundle</name>
<description>JSR 349's RI, Hibernate Validator version ${hibernate-validator.version} and its dependencies repackaged as OSGi bundle</description>
<developers>
<developer>
<id>ss141213</id>
<name>Sahoo</name>
<organization>Sun Microsystems, Inc.</organization>
<roles>
<role>developer</role>
</roles>
</developer>
</developers>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<useDefaultManifestFile>true</useDefaultManifestFile>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<classpathLayoutType>custom</classpathLayoutType>
<customClasspathLayout>${artifact.artifactId}.${artifact.extension}</customClasspathLayout>
</manifest>
</archive>
<excludes>
<exclude>**/.ade_path/**</exclude>
</excludes>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.4.0</version>
<configuration>
<instructions>
<Embed-Dependency>
<!-- Only specify root artifacts that need to be embedded, everything else
will be pulled in automatically based on Private-Package settings. -->
*; artifactId=hibernate-validator; inline=true
</Embed-Dependency>
<Export-Package>
javax.validation.*; version=${javax.validation.osgi.version},
org.hibernate.validator.*; version=${hibernate-validator.version},
org.glassfish.validation; version=${hibernate-validator.version}
</Export-Package>
<Private-Package>
<!-- JBoss logging is used by Hibernate Validator as of version 4.3.0.Final.
We must repackage it privately in this bundle.
-->
org.jboss.logging.*,com.fasterxml.*
</Private-Package>
<Import-Package>
<!--
- bean validator has optional dependency on JPA API. More over, it relies on
JPA 2.0, as it tries to dynamically load javax.persistence.PersistenceUtil.class,
which is a JPA 2 class.
- jboss.logging has the following optional dependencies (see manifest in
jboss-logging-*.jar):
org.apache.log4j, org.jboss.logmanager, org.slf4j, org.slf4j.spi
- Hibernate Validator has optional dependencies on (see manifest in
hibernate-validator-*.jar): javax.persistence, org.joda.time, org.jsoup, org.jsoup.safety
javax.enterprise.inject.*; resolution:=optional,
-->
org.slf4j; org.slf4j.spi; org.slf4j.helpers; version=${slf4j.version}; resolution:=optional,
javax.persistence.*; version="2.0"; resolution:=optional,
org.joda.time; resolution:=optional; version="[1.6.0,2.0.0)",
org.jsoup.*; resolution:=optional; version="[1.5.2,2.0.0)",
org.apache.log4j; resolution:=optional,
org.jboss.logmanager; resolution:=optional,
javax.el;version="[2.2,4]",
com.sun.el,
com.sun.el.*,
com.sun.el.lang.*,
com.sun.el.util.*,
javax.enterprise.inject.*; resolution:=optional,
javax.enterprise.context.*; resolution:=optional,
javax.enterprise.event.*; resolution:=optional,
javax.enterprise.util.*; resolution:=optional,
javax.interceptor.*; resolution:=optional,
com.thoughtworks.paranamer.*; resolution:=optional,
javafx.beans.value.*; resolution:=optional,
javafx.application; resolution:=optional,
org.apache.logging.log4j.*; resolution:=optional,
org.hibernate.validator.*; version=${hibernate-validator.version},
*
</Import-Package>
<!--
See https://hibernate.onjira.com/browse/HV-562 which I have filed against hibernate validator.
It's a bug in hibernate validator the way it detects JPA. It uses thread's context classloader to
see if JPA classes are available and then goes onto instantiate its JPATraversableResolver which
has staic dependency on JPA classes. It should have used its own class loader to detect existence
of JPA classes. If we don't add this DynamicImport-Package, what could happen is that at the time
of resolution of hibernate-validator, it's optional dependency on javax.persistence may not be
satisfied, so this bundle won't be able to load jpa classes, yet when it uses TCL to detect JPA,
that might return true. Based on this outcome, it could go onto use JPATraversableResolver and
eventually fail with NCDFE. Adding a DynamicImport-Package helps rewiring this bundle to JPA late.
-->
<DynamicImport-Package>javax.persistence; javax.persistence.*; version="2.0"</DynamicImport-Package>
<Implementation-Version>
${hibernate-validator.version}
</Implementation-Version>
</instructions>
<!-- Maven uses the output directory (target/classes)
rather than the final bundle, when compiling against
projects in the same reactor (ie. the same build).
Since this jar comprises of classes that come from
some other jar and other modules depend on this
artifact, we need to unpack.
-->
<unpackBundle>true</unpackBundle>
</configuration>
<executions>
<execution>
<id>osgi-bundle</id>
<phase>package</phase>
<goals>
<goal>bundle</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>get-sources</id>
<phase>process-sources</phase>
<goals>
<goal>unpack</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/sources</outputDirectory>
<stripVersion>true</stripVersion>
<artifactItems>
<artifactItem>
<groupId>org.hibernate.validator</groupId>
<artifactId>hibernate-validator</artifactId>
<version>${hibernate-validator.version}</version>
<classifier>sources</classifier>
<overWrite>false</overWrite>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<id>add-source</id>
<phase>compile</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources>
<source>${project.build.directory}/sources</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.hibernate.validator</groupId>
<artifactId>hibernate-validator</artifactId>
<optional>true</optional>
</dependency>
<!-- This dependency is not required in latest hibernate jars. Keeping this in commented form for reference.
<dependency>-->
<!--
Although hibernate validator uses maven-shade-plugin to repackage com.googlecode.jtype classes
bu org.hibernate.validator.jtype classes, the shade plugin seems to leave behind some
constant pool entries referring to google classes, so we need to package google jtype classes as well.
I have asked Emmanuel Bernard about this. It appears to be a bug in shade plugin or HV.
Because of shade-plugin, the dependency is remove from hibernate-validator pom, so we need to add it
here so that we can package these classes.
-->
<!--<groupId>com.googlecode.jtype</groupId>
<artifactId>jtype</artifactId>
<optional>true</optional>
</dependency>-->
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
<optional>true</optional>
</dependency>
<!--
Remove this once HK2 config bean generation issue is fixed when using 2.0.0 based version of javax.validation APIs.
Maven bundle plugin while determining dependencies of hibernate-validator will find javax.validation.validation-api in its
dependencies list and pick the version value based on the javax.validation.validation-api dependency defined
in parent project i.e., nuclues' pom.xml.
Hence explicitly adding the required version as we use different version for compilation purposes.
-->
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>${javax.validation.version}</version>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging-annotations</artifactId>
<optional>true</optional>
</dependency>
</dependencies>
<!--
This module repackages various maven artifacts and artifacts like hibernate-validator does not
have java-docs published. Hence, we cannot repackage the java-docs. We skip java-doc
generation and use empty java-doc plugin
to make Nexus release job succeed.
-->
<profiles>
<profile>
<!-- generate empty javadoc jar -->
<id>release-phase2</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>create-empty-javadoc-jar</id>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<classesDirectory>
${project.build.directory}/javadoc
</classesDirectory>
<classifier>javadoc</classifier>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>
