#Maven help
pine arrow
This is about the Quests project https://github.com/PikaMug/Quests
Basically, the current setup produces two sets of jars from both the dist and main modules, the dist target being the completed jar. I suspect this is detrimental to the storage and processing time on its maven repository, but also means the dependency snippet is as follows:
<dependency>
<groupId>me.blackvein.quests</groupId>
<artifactId>quests-dist</artifactId>
<version>4.1.2</version>
</dependency>
I would prefer to move to a more standardized approach, as I have not seen any other Bukkit projects utilizing the assembly plugin and all-jar file. Additionally, it would be great to have the artifact ID simply be quests instead. If anyone is able to help with this transition I'd be glad to compensate for your time.
uncut lantern
from another discussion I'm pretty sure it is the standard approach
as for the artifact question, why do dependencies need your NMS implementation
they should be able to depend on quests just fine
pine arrow
This being standard strikes me as odd (granted, I didn't set up this portion of the project), but that's a great point about dependencies. I'll just rename quests-main to quests, use that for the artifact and call it good enough, pending complaint from the repo host. Thanks!
uncut lantern
quests-dist doesnt even need to be put in the maven repo
pine arrow
Agreed but I'm not sure how to exclude it.
