- DO I NEED THE NEXUS 2 DLL FILE FOR IT TO WORK MOD
- DO I NEED THE NEXUS 2 DLL FILE FOR IT TO WORK FULL
DO I NEED THE NEXUS 2 DLL FILE FOR IT TO WORK MOD
Whenever you want to switch between mods, youll have to cut and paste the files in the game folder somewhere else and replace them with the game files of the mod you want to play. I've also tried the mod Simple Lock-On, but I couldn't get that to work either. I tried renaming LockOnSSE.dll to LockOn.DLL, but that didn't help. The deploy goal of the plugin is mapped to the deploy phase of the Maven build.Īlso notice that, as discussed, we do not need staging functionality in a simple deployment of -SNAPSHOT artifacts to Nexus, so that is fully disabled via the element.īy default, the deploy goal includes the staging workflow, which is recommended for release builds. This will overwrite files, so make sure to copy a backup first into a different folder. I noticed a couple weird things, like that the file is actually called LockOnSSE.dll, and that the mod's MCM menu mentions FISS and not FISSES, but I don't know if they matter. So, the first step in using another deployment plugin in the deploy phase is to disable the existing, default mapping: However, unlike other components that may actually change throughout the lifecycle of a project, the Maven Repository Manager is highly unlikely to change, so that flexibility is not required. The only reason to use the maven-deploy-plugin is to keep open the option of using an alternative to Nexus in the future – for example, an Artifactory repository.
DO I NEED THE NEXUS 2 DLL FILE FOR IT TO WORK FULL
Because of that fact, Sonatype built a Nexus specific plugin – the nexus-staging-maven-plugin – that is actually designed to take full advantage of the more advanced functionality that Nexus has to offer – functionality such as staging.Īlthough for a simple deployment process we do not require staging functionality, we will go forward with this custom Nexus plugin since it was built with the clear purpose to talk to Nexus well. The maven-deploy-plugin is a viable option to handle the task of deploying to artifacts of a project to Nexus, but it was not built to take full advantage of what Nexus has to offer.
By default, Maven handles the deployment mechanism via the maven-deploy-plugin – this mapped to the deployment phase of the default Maven lifecycle: