You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Andy Glick (JIRA)" <ji...@apache.org> on 2018/08/13 15:14:00 UTC

[jira] [Commented] (GROOVY-8750) the jar file, and only the jar file is missing from a large number of releases on Maven Central

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

Andy Glick commented on GROOVY-8750:
------------------------------------

it turns out that this isn't a problem, the groovy-all artifact went from being a jar reference to a pom only reference

> the jar file, and only the jar file is missing from a large number of releases on Maven Central
> -----------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-8750
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8750
>             Project: Groovy
>          Issue Type: Bug
>          Components: groovy-jdk, groovy-runtime
>            Reporter: Andy Glick
>            Priority: Major
>             Fix For: 2.6.0-alpha-3, 3.0.0-alpha-2, 2.6.0-alpha-4, 3.0.0-alpha-3
>
>
> it looks as if sometime after the 1st of the year 2018, something went wrong with the CI process and none of the groovy releases at the maven central repo released in 2018 have a jar file associated with them – I do know that his seems ridiculous on the face of it, but my builds have been breaking and when I went to find out why I found that this situation seems to be in effect 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)