The Teamer class is not contained in the teamer package like all other Teamer related classes. A refactor could change this, but would constitute a breaking change with the relevant version. It is also not suggested to maintain a redirect class. If the decision is made to use a redirect class, this should be done through a maven plugin - it might be possible that this would be a custom plugin.
|
package net.juligames.core.minigame.api; |
|
|
|
import de.bentzin.tools.collection.Subscription; |
|
import net.juligames.core.minigame.api.team.Team; |
|
import net.juligames.core.minigame.api.team.TeamColor; |
|
import net.juligames.core.minigame.api.team.procedures.InsertionProcedure; |
|
import net.juligames.core.minigame.api.team.procedures.RandomInsertionProcedure; |
|
import org.jetbrains.annotations.ApiStatus; |
|
import org.jetbrains.annotations.NotNull; |
|
import org.jetbrains.annotations.Range; |
|
|
|
import java.util.*; |
|
import java.util.concurrent.atomic.AtomicBoolean; |
|
import java.util.function.BiConsumer; |
|
import java.util.function.Predicate; |
|
import java.util.stream.Collectors; |
|
|
|
/** |
|
* @author Ture Bentzin |
|
* 18.12.2022 |
|
*/ |
|
@SuppressWarnings({"ProtectedMemberInFinalClass", "unused"}) |
|
public final class Teamer { |
The Teamer class is not contained in the teamer package like all other Teamer related classes. A refactor could change this, but would constitute a breaking change with the relevant version. It is also not suggested to maintain a redirect class. If the decision is made to use a redirect class, this should be done through a maven plugin - it might be possible that this would be a custom plugin.
JuliGamesCore/MiniGameAPI/src/main/java/net/juligames/core/minigame/api/Teamer.java
Lines 1 to 23 in decf81a