[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Resolved] (RNG-38) Wrong badge on Github
From:       "Gilles (JIRA)" <jira () apache ! org>
Date:       2017-06-30 20:39:00
Message-ID: JIRA.13062597.1491611087000.149450.1498855140172 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/RNG-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Gilles resolved RNG-38.
-----------------------
    Resolution: Workaround

Badges were manually added.

The "README.md" file should not be re-generated before there is a solution to \
COMMONSSITE-90 for modular components.


> Wrong badge on Github
> ---------------------
> 
> Key: RNG-38
> URL: https://issues.apache.org/jira/browse/RNG-38
> Project: Commons RNG
> Issue Type: Bug
> Reporter: Gilles
> Assignee: Artem Barger
> Priority: Minor
> Labels: github, readme, web-site
> Fix For: 1.1
> 
> 
> The (auto-generated) "README.md" file contains the following line:
> {noformat}
> [![Maven Central](https://maven-badges.herokuapp.com/maven-central/org.apache.common \
> s/commons-rng/badge.svg)](https://maven-badges.herokuapp.com/maven-central/org.apache.commons/commons-rng/)
>  {noformat}
> which results in the badge showing "maven central unknown" on the GitHub mirror \
> main page (and clicking on it leads to a page, on Maven Central, that shows: "No \
> records found, try new search criteria").



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[prev in list] [next in list] [prev in thread] [next in thread]