[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-23 Thread Gilles (JIRA)

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

Gilles commented on RNG-38:
---

bq. badge \[...\] has to refer to existing artifact within maven central

Can we add a badge for each of the user modules (since downloading 
{{commons-rng-parent}} would be useless for a user)?

If so, the general problem would still remain that the "README.md" file which 
the commons-build-plugin automatically generates is not suitable for a modular 
component.


> 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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-23 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on RNG-38:
---

Github user coveralls commented on the issue:

https://github.com/apache/commons-rng/pull/3
  

[![Coverage 
Status](https://:/builds/12102911/badge)](https://:/builds/12102911)

Coverage decreased (-0.02%) to 96.919% when pulling 
**3179fd6a6bbbdb3cd2fb492ad27b7dfadcb21fb4 on C0rWin:RNG-38** into 
**acb61071ae681732a5d70e6d2587dc95a6eb64d4 on apache:master**.



> 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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-23 Thread Artem Barger (JIRA)

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

Artem Barger commented on RNG-38:
-

Changed PR to have badge point on parent project instead.

> 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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-23 Thread Artem Barger (JIRA)

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

Artem Barger commented on RNG-38:
-

Here the problem, to add this badge it has to refer to existing artifact within 
maven central. So we can add it to each project and make root point to the 
parent.

> 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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-23 Thread Gilles (JIRA)

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

Gilles commented on RNG-38:
---

Do you mean that each module must have its own badge?
It's not such a good idea to only point to the "low-level" {{commons-rng-core}} 
module since user-level functionality is rather in  {{commons-rng-client-api}}, 
{{commons-rng-simple}} and {{commons-rng-sampling}}.

> 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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on RNG-38:
---

Github user coveralls commented on the issue:

https://github.com/apache/commons-rng/pull/3
  

[![Coverage 
Status](https://:/builds/12095968/badge)](https://:/builds/12095968)

Coverage remained the same at 96.934% when pulling 
**fc42e1d03ef2232ee243d9a1a7cd2db37b22ba14 on C0rWin:RNG-38** into 
**acb61071ae681732a5d70e6d2587dc95a6eb64d4 on apache:master**.



> 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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-06-22 Thread Artem Barger (JIRA)

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

Artem Barger commented on RNG-38:
-

https://github.com/apache/commons-rng/pull/3

> Wrong badge on Github
> -
>
> Key: RNG-38
> URL: https://issues.apache.org/jira/browse/RNG-38
> Project: Commons RNG
>  Issue Type: Bug
>Reporter: Gilles
>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.commons/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)


[jira] [Commented] (RNG-38) Wrong badge on Github

2017-04-14 Thread Gilles (JIRA)

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

Gilles commented on RNG-38:
---

Does the generator support 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
>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.commons/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.3.15#6346)