Shopkeepers/pom.xml

193 lines
5.2 KiB
XML
Raw Normal View History

<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/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.nisovin.shopkeepers</groupId>
<artifactId>sk-parent</artifactId>
<version>${revision}</version>
<relativePath>modules/parent/</relativePath>
</parent>
<artifactId>sk-root</artifactId>
<packaging>pom</packaging>
<name>SK Root</name>
<url>${shopkeepers.repository.url}</url>
2018-06-02 09:15:02 -07:00
<scm>
<connection>${shopkeepers.repository.connection}</connection>
<developerConnection>${shopkeepers.repository.developerConnection}</developerConnection>
<url>${shopkeepers.repository.url}</url>
2018-06-02 09:15:02 -07:00
</scm>
<profiles>
<profile>
<id>jenkins</id>
<properties>
<vnp-version>${project.version}-${buildNumber}</vnp-version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.2</version>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
<configuration>
<doCheck>true</doCheck>
<revisionOnScmFailure>no-rev</revisionOnScmFailure>
<!-- This only works within the child modules -->
<scmDirectory>${project.parent.relativePath}</scmDirectory>
<shortRevisionLength>7</shortRevisionLength>
</configuration>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>release</id>
<properties>
<vnp-version>${project.version}</vnp-version>
</properties>
</profile>
</profiles>
<modules>
<module>modules/api</module>
<module>modules/main</module>
Update for MC 1.14 (Spigot 1.14-pre5) * Dropped support for MC 1.13. This version only supports MC 1.14. * If you are upgrading, make sure that you have successfully updated shopkeepers to 1.13 first. Migration from older MC are not supported and might not work. Reverting to older versions isn't supported either. * Removed pre 1.13 sheep color migration. * Villager shopkeepers: * Changed default profession from farmer to 'none'. * Priest villagers get converted to 'cleric' and blacksmiths become 'armorer'. Previous regular farmer villagers stay farmers (but they look different now). * Changed the items representing the villager professions in the editor. * Note: Wandering traders are not a villager sub-variant, but a different mob type. * Ocelot shopkeepers of cat types have been converted to corresponding cat shopkeepers. You might have to adapt your players' permissions, since cat and ocelot shopkeepers require different permissions now. With this migration players can end up with cat shopkeepers even though they don't have the permission to freshly create those if they wanted. The different cat types are represented by colored leather armor inside the editor. * Any settings affecting regular villagers will affect wandering traders as well now. There are no settings (for now?) to handle wandering traders differently. When preventing regular villagers from spawning, the trader llamas of the wandering trader are prevented from spawning as well. When hiring a wandering trader its leashed llama should get unleashed due to the removal of the wandering trader. * Added: Sign shops can now switch between different wood types. TODO: * This has not yet been tested. Spigot 1.14-pre5 seems to still have some other issues which prevent me from testing this currently. * New entities have not yet been tested. * Support for changing between different villager biome types would be nice.
2019-04-24 18:18:01 -07:00
<module>modules/v1_14_R1</module>
<module>modules/v1_15_R1</module>
<module>modules/v1_16_R1</module>
<module>modules/v1_16_R2</module>
2020-11-03 13:37:52 -08:00
<module>modules/v1_16_R3</module>
<module>modules/dist</module>
</modules>
<repositories>
<repository>
<id>sk89q-repo</id>
<url>http://maven.sk89q.com/repo/</url>
</repository>
<!-- WorldGuard/Edit transitively requires paper dependencies -->
<repository>
<id>paper-repo</id>
<url>https://papermc.io/repo/repository/maven-public/</url>
</repository>
<repository>
<name>Citizens2 repository</name>
<id>everything</id>
<url>http://repo.citizensnpcs.co</url>
</repository>
<repository>
<id>vault-repo</id>
<url>http://nexus.hc.to/content/repositories/pub_releases</url>
</repository>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
<repository>
<id>bstats-repo</id>
2019-06-17 07:14:38 -07:00
<url>https://repo.codemc.org/repository/maven-public</url>
</repository>
</repositories>
<!-- Main dependencies, placed in this parent so that the root eclipse project finds them -->
<dependencies>
<!-- Includes Bukkit, required for Spigot-specific (optional) features -->
<dependency>
<groupId>org.spigotmc</groupId>
<artifactId>spigot-api</artifactId>
</dependency>
Changed how items are getting defined in the config. Internally this new format uses Bukkit's item serialization for parsing the item data, which allows it to support the specification of arbitrary item data and hopefully not require any major updating/maintenance for future minecraft versions. At the same time it tries to stay (slightly) more user-friendly than Bukkit's item serialization by omitting any data that can be restored by the plugin, by avoiding one level of nesting between the item type and item data, by translating ampersand ('&') color codes in display name and lore, and by offering a compact representation for specifying an item only by its type. This change also allows a more detailed specification of some of the editor button items. However, many editor buttons still miss corresponding config settings. Also keep in mind that the display name and lore for these button items get specified via corresponding message settings, so any specified item display name and lore will get replaced by that. When checking if an in-game item matches the item data specified in the config, only the specified data gets compared. So this does not check for item data equality, but instead the checked item is able to contain additional data but still get matched (like before, but previously this was limited to checking display name and lore). The previous item data gets automatically migrated to the new format (config version 2). Other changes: * Internal: Moved config migrations into a separate package. * Internal: Moved some function(s) into ConfigUtils. * Internal: Slightly changed how the plugin checks whether the high currency is enabled. * Internal: Avoiding ItemStack#hasItemMeta calls before getting an item's ItemMeta, since this might be heavier than simply getting the ItemMeta directly and performing only the relevant checks on that. Internally ItemStack#hasItemMeta checks emptiness for all item attributes and might (for CraftItemStacks) even first copy all the item's data into a new ItemMeta object. And even if the item actually has no data (Bukkit ItemStack with null ItemMeta), ItemStack#getItemMeta will simply create a new empty ItemMeta object without having to copy any data, so this is still a similarly lightweight operation anyways. * Internal: Added ItemData tests. Unfortunately this requires CraftBukkit as test dependency.
2019-08-17 19:51:49 -07:00
<dependency>
<groupId>org.bukkit</groupId>
<artifactId>craftbukkit</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
Changed how items are getting defined in the config. Internally this new format uses Bukkit's item serialization for parsing the item data, which allows it to support the specification of arbitrary item data and hopefully not require any major updating/maintenance for future minecraft versions. At the same time it tries to stay (slightly) more user-friendly than Bukkit's item serialization by omitting any data that can be restored by the plugin, by avoiding one level of nesting between the item type and item data, by translating ampersand ('&') color codes in display name and lore, and by offering a compact representation for specifying an item only by its type. This change also allows a more detailed specification of some of the editor button items. However, many editor buttons still miss corresponding config settings. Also keep in mind that the display name and lore for these button items get specified via corresponding message settings, so any specified item display name and lore will get replaced by that. When checking if an in-game item matches the item data specified in the config, only the specified data gets compared. So this does not check for item data equality, but instead the checked item is able to contain additional data but still get matched (like before, but previously this was limited to checking display name and lore). The previous item data gets automatically migrated to the new format (config version 2). Other changes: * Internal: Moved config migrations into a separate package. * Internal: Moved some function(s) into ConfigUtils. * Internal: Slightly changed how the plugin checks whether the high currency is enabled. * Internal: Avoiding ItemStack#hasItemMeta calls before getting an item's ItemMeta, since this might be heavier than simply getting the ItemMeta directly and performing only the relevant checks on that. Internally ItemStack#hasItemMeta checks emptiness for all item attributes and might (for CraftItemStacks) even first copy all the item's data into a new ItemMeta object. And even if the item actually has no data (Bukkit ItemStack with null ItemMeta), ItemStack#getItemMeta will simply create a new empty ItemMeta object without having to copy any data, so this is still a similarly lightweight operation anyways. * Internal: Added ItemData tests. Unfortunately this requires CraftBukkit as test dependency.
2019-08-17 19:51:49 -07:00
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>hamcrest-library</artifactId>
Changed how items are getting defined in the config. Internally this new format uses Bukkit's item serialization for parsing the item data, which allows it to support the specification of arbitrary item data and hopefully not require any major updating/maintenance for future minecraft versions. At the same time it tries to stay (slightly) more user-friendly than Bukkit's item serialization by omitting any data that can be restored by the plugin, by avoiding one level of nesting between the item type and item data, by translating ampersand ('&') color codes in display name and lore, and by offering a compact representation for specifying an item only by its type. This change also allows a more detailed specification of some of the editor button items. However, many editor buttons still miss corresponding config settings. Also keep in mind that the display name and lore for these button items get specified via corresponding message settings, so any specified item display name and lore will get replaced by that. When checking if an in-game item matches the item data specified in the config, only the specified data gets compared. So this does not check for item data equality, but instead the checked item is able to contain additional data but still get matched (like before, but previously this was limited to checking display name and lore). The previous item data gets automatically migrated to the new format (config version 2). Other changes: * Internal: Moved config migrations into a separate package. * Internal: Moved some function(s) into ConfigUtils. * Internal: Slightly changed how the plugin checks whether the high currency is enabled. * Internal: Avoiding ItemStack#hasItemMeta calls before getting an item's ItemMeta, since this might be heavier than simply getting the ItemMeta directly and performing only the relevant checks on that. Internally ItemStack#hasItemMeta checks emptiness for all item attributes and might (for CraftItemStacks) even first copy all the item's data into a new ItemMeta object. And even if the item actually has no data (Bukkit ItemStack with null ItemMeta), ItemStack#getItemMeta will simply create a new empty ItemMeta object without having to copy any data, so this is still a similarly lightweight operation anyways. * Internal: Added ItemData tests. Unfortunately this requires CraftBukkit as test dependency.
2019-08-17 19:51:49 -07:00
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.sk89q.worldguard</groupId>
<artifactId>worldguard-legacy</artifactId>
<version>7.0.0-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.github.TownyAdvanced</groupId>
<artifactId>Towny</artifactId>
<version>0.96.2.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>net.citizensnpcs</groupId>
<artifactId>citizens</artifactId>
<version>2.0.16-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>net.milkbowl.vault</groupId>
<artifactId>VaultAPI</artifactId>
<version>1.6</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.bstats</groupId>
<artifactId>bstats-bukkit</artifactId>
2019-06-17 07:14:38 -07:00
<version>1.5</version>
<scope>compile</scope>
</dependency>
</dependencies>
<!-- Also compile at root to avoid some issues in Eclipse -->
<build>
<sourceDirectory>src/main/java</sourceDirectory>
<plugins>
<!-- Manually add sources of dependencies -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<id>add-additional-sources</id>
<phase>generate-sources</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources>
<source>src/api/java</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<executions>
<execution>
<id>compile</id>
<phase>compile</phase>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>