dspace-api-lang
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-api-lang</artifactId>
<version>9.0.1</version>
</dependency><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.dspace</groupId>
<artifactId>dspace-api-lang</artifactId>
<name>DSpace I18N :: Language Packs</name>
<description>
DSpace API Language Packs to support multiple languages on backend.
</description>
<version>9.0.1</version>
<url>https://github.com/dspace/dspace-api-lang</url>
<organization>
<name>LYRASIS</name>
<url>https://www.dspace.org</url>
</organization>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>${project.build.sourceEncoding}</project.reporting.outputEncoding>
<java.version>17</java.version>
</properties>
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<excludes>
<exclude>**/*.properties.UTF-8</exclude>
</excludes>
</resource>
</resources>
<!-- Define Maven Plugin Settings / versions. -->
<pluginManagement>
<plugins>
<!-- Use to enforce a particular version of Java and ensure no conflicting dependencies -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.4.1</version>
<executions>
<execution>
<id>enforce-java</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireJavaVersion>
<version>${java.version}</version>
</requireJavaVersion>
<requireMavenVersion>
<version>[3.8,)</version>
</requireMavenVersion>
</rules>
</configuration>
</execution>
<!-- Make sure that we do not have conflicting dependencies-->
<execution>
<id>enforce-versions</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<DependencyConvergence />
</rules>
</configuration>
</execution>
</executions>
</plugin>
<!-- Used to compile all Java classes -->
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
<configuration>
<release>${java.version}</release>
</configuration>
</plugin>
<!-- Used to package all DSpace JARs -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>3.3.0</version>
<configuration>
<archive>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
</manifest>
</archive>
</configuration>
</plugin>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.8</version>
</plugin>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>3.7.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>3.6.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>3.3.1</version>
</plugin>
<!-- Used to generate a new release via Sonatype (see release profile). -->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>0.8.0</version>
</plugin>
<!-- Used to generate JavaDocs for new releases (see release profile). -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.11.2</version>
<configuration>
<!-- Never fail a build based on Javadoc errors -->
<failOnError>false</failOnError>
</configuration>
</plugin>
<!-- Used to generate source JARs for new releases (see release profile). -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>3.3.1</version>
</plugin>
<!-- Used to sign new releases via GPG (see release profile). -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>3.2.7</version>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<!-- Specify our settings for new releases via 'mvn release:*' -->
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>3.1.1</version>
<configuration>
<!-- During release:prepare and release:perform, pass the "release" property to enable the
"release" profile (and enable/disable other profiles based on whether they need releasing) -->
<arguments>-Drelease</arguments>
<goals>deploy</goals>
<!-- Suggest tagging the release in SCM as "dspace-[version]" -->
<tagNameFormat>dspace-api-lang-@{project.version}</tagNameFormat>
<!-- Auto-Version all modules the same as the parent module -->
<autoVersionSubmodules>true</autoVersionSubmodules>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>native2ascii</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<configuration>
<target>
<!-- Run 'native2ascii' to encode UTF-8 characters in properties files. -->
<native2ascii encoding="UTF8" src="${basedir}/src/main/native2ascii" dest="${basedir}/src/main/resources" includes="**/*.properties.UTF-8" ext="" />
</target>
</configuration>
<executions>
<execution>
<phase>generate-resources</phase>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
<dependencies>
<!-- Required dependency for native2ascii to function -->
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>${java.version}</version>
<scope>system</scope>
<!-- Path to tools.jar (containing native2ascii tool) is determined by a profile (see below) -->
<systemPath>${toolsjar}</systemPath>
</dependency>
<dependency>
<groupId>org.apache.ant</groupId>
<artifactId>ant-nodeps</artifactId>
<version>1.8.1</version>
</dependency>
<dependency>
<groupId>org.apache.ant</groupId>
<artifactId>ant</artifactId>
<version>1.10.11</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
</profile>
<!-- Determine path to Java Tools JAR. This JAR contains the 'native2ascii' tool (required above by maven-antrun-plugin)-->
<!-- In most platforms Unix/Windows it's named tools.jar. But, on Mac it's classes.jar (see next profile) -->
<profile>
<id>default-java-tools</id>
<activation>
<activeByDefault>true</activeByDefault>
<file>
<exists>${java.home}/../lib/tools.jar</exists>
</file>
</activation>
<properties>
<toolsjar>${java.home}/../lib/tools.jar</toolsjar>
</properties>
</profile>
<profile>
<id>mac-java-tools</id>
<activation>
<activeByDefault>false</activeByDefault>
<file>
<exists>${java.home}/../Classes/classes.jar</exists>
</file>
</activation>
<properties>
<toolsjar>${java.home}/../Classes/classes.jar</toolsjar>
</properties>
</profile>
<!--
The 'release' profile is used by the 'maven-release-plugin' (see above)
to actually perform a DSpace lang packs release to Maven Central.
This profile contains settings which are ONLY enabled when performing
a DSpace release. See alse https://wiki.duraspace.org/display/DSPACE/Release+Procedure
-->
<profile>
<id>release</id>
<activation>
<activeByDefault>false</activeByDefault>
<!-- Enable this profile if we are doing a release (-Drelease) -->
<property>
<name>release</name>
</property>
</activation>
<build>
<plugins>
<!--
Configure Central Publishing Plugin for new releases via Sonatype.
See: https://central.sonatype.org/publish/publish-portal-maven/
A few notes on how this plugin works:
1. In your settings.xml, your user/password tokens MUST be specified for a <server> tag
with <id>central</id>. Otherwise, you will see a 401 Unauthorized error.
2. The <distributionManagement> POM section is no longer needed. This plugin defaults to
uploading releases to Central Portal (https://central.sonatype.com/publishing)
and -SNAPSHOT releases to https://central.sonatype.com/repository/maven-snapshots/
3. Sonatype has publishing *requirements* which must be met. Our POM is already configured to
meet those requirements: https://central.sonatype.org/publish/requirements/
-->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<extensions>true</extensions>
</plugin>
<!-- Per Sonatype publishing requirements, generate Source JAR files -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<goals>
<goal>jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Per Sonatype publishing requirements, sign any new releases via GPG.
NOTE: you may optionally specify the "gpg.passphrase" in your settings.xml -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<developers>
<developer>
<name>DSpace Committers</name>
<email>dspace-devel@googlegroups.com</email>
<url>https://wiki.lyrasis.org/display/DSPACE/DSpace+Committers</url>
<roles>
<role>committer</role>
</roles>
</developer>
</developers>
<contributors>
<contributor>
<name>DSpace Contributors</name>
<email>dspace-tech@googlegroups.com</email>
<url>https://wiki.lyrasis.org/display/DSPACE/DSpaceContributors</url>
<roles>
<role>developer</role>
</roles>
</contributor>
</contributors>
<!--
Information about the SCM repository where source code exists.
-->
<scm>
<connection>scm:git:git@github.com:DSpace/dspace-api-lang.git</connection>
<developerConnection>scm:git:git@github.com:DSpace/dspace-api-lang.git</developerConnection>
<url>https://github.com/DSpace/dspace-api-lang</url>
<tag>dspace-api-lang-9.0.1</tag>
</scm>
<licenses>
<license>
<name>DSpace BSD License</name>
<url>https://raw.github.com/DSpace/DSpace/main/LICENSE</url>
<distribution>repo</distribution>
<comments>
A BSD 3-Clause license for the DSpace codebase.
</comments>
</license>
</licenses>
<issueManagement>
<system>GitHub</system>
<url>https://github.com/DSpace/DSpace/issues</url>
</issueManagement>
</project>