You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/06/02 17:07:00 UTC

[jira] [Comment Edited] (MSHADE-395) 3.3.0-SNAPSHOT not available in repository

    [ https://issues.apache.org/jira/browse/MSHADE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355865#comment-17355865 ] 

Michael Osipov edited comment on MSHADE-395 at 6/2/21, 5:06 PM:
----------------------------------------------------------------

11th commandment: Thou shalt not rely on snapshots.


was (Author: michael-o):
11th commandment: One shall not rely on snapshots.

> 3.3.0-SNAPSHOT not available in repository
> ------------------------------------------
>
>                 Key: MSHADE-395
>                 URL: https://issues.apache.org/jira/browse/MSHADE-395
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Gabriel Wolf
>            Priority: Major
>              Labels: 16, 3.3.0, java, snapshot
>
> Hey, i am one of the developers from BetonQuest [https://github.com/BetonQuest/BetonQuest] and we use the maven-shade-plugin.
>  Not we want/need to update to java 16.
> First i had the following issue: 
>  [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project betonquest: Error creating shaded jar: Unsupported class file major version 60 -> [Help 1]
> After a small research i found the following: [https://www.reddit.com/r/Maven/comments/mw58hq/mavenshadeplugin_java_16/gvgg6hd/]
> So it seems that 3.3.0-SNAPSHOT ([https://repository.apache.org/content/repositories/snapshots/]) solved my problem, but i run into the same problem, that the snapshot can not be downloaded.
> As a workaround, i tried to run mvn install by my own, and everything works as wanted.
> But this is not working on my buildserver (github actions).
> Is the artifact broken in the repository or is there something else wrong?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)