fix(deps): Update groupid for onejar-maven-plugin #8242
Conversation
The maintained plugin was discontinued under Drew Stovall and is now maintained under com.jolira. More details in https://groups.google.com/g/mojohaus-dev/c/rvMn64oLZ4g Signed-off-by: Ronny Trommer <[email protected]>
indigo423
force-pushed
the
ronny/fix-maven-plugin
branch
from
36650cb to
23c168e
Compare
cgorantla
left a comment
cgorantla
left a comment
There was a problem hiding this comment.
https://mvnrepository.com/artifact/com.jolira/onejar-maven-plugin seems to be older than https://mvnrepository.com/artifact/org.dstovall/onejar-maven-plugin/1.4.4
not understanding the intent here.
The original source for org.dstovall doesn't exist anymore and went away. It was forked to GitHub and was made available now under com.jolira. |
|
Do you have it backwards? org.dstovall » onejar-maven-plugin » 1.4.4 -> Oct 09, 2013 com.jolira » onejar-maven-plugin » 1.4.4 -> Dec 13, 2011 |
|
I did some deeper investigation, the code is exactly the same. The com.jolira is preferred because it's in maven central and the org.dstovall was moved to a redhat maven repository. The major issue is still the same, both are completely unmaintained since over 10 years now. The newest fork of it is the https://github.com/greening/unojar-maven-plugin that give us a 6 year outdated unmaintained plugin that is half as outdated as the other ones. To really solve this problem we need to get rid of the onejar plugin and need to migrate to something else, using the maven-shade-plugin. |
3 participants
The maintained plugin was discontinued under Drew Stovall and is now maintained under com.jolira. More details in https://groups.google.com/g/mojohaus-dev/c/rvMn64oLZ4g
https://mvnrepository.com/artifact/com.jolira/onejar-maven-plugin