Skip to content

Conversation

cquiroz
Copy link
Contributor

@cquiroz cquiroz commented Jun 9, 2016

This PR contains an implementation of large part of the java util logging package. This PR was submitted to scala-js as scala-js/scala-js#2410

@@ -1,9 +1,9 @@
# scalajs-java-logging

[![Build Status](https://travis-ci.org/scala-js/scala-js-java-logging.svg?branch=master)](https://travis-ci.org/scala-js/scala-js-java-logging)
[![Scala.js](https://www.scala-js.org/assets/badges/scalajs-0.6.9.svg)](https://www.scala-js.org/)
[![Scala.js](https://www.scala-js.org/assets/badges/scalajs-0.6.8.svg)](https://www.scala-js.org/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should not change this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The svg for 6.9 is missing. I guess the solution is to add that badge to scala-js

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cquiroz You are actually right to change it to 0.6.8. But ideally that would be in a separate PR, as it irrelevant to this PR.

@nicolasstucki
Copy link
Contributor

That is all. Otherwise LGTM.

@cquiroz
Copy link
Contributor Author

cquiroz commented Jun 10, 2016

Is it ok to add my name to the list of developers?

@sjrd
Copy link
Member

sjrd commented Jun 10, 2016

Is it ok to add my name to the list of developers?

Good question. According to https://maven.apache.org/pom.html#Developers, I don't think you should. They say:

Developers are presumably members of the project's core development. Note that, although an organization may have many developers (programmers) as members, it is not good form to list them all as developers, but only those who are immediately responsible for the code. A good rule of thumb is, if the person should not be contacted about the project, they need not be listed here.

From that paragraph, I interpret the term "developer" more as "maintainer", i.e., people who are in charge of the repository.

If we had a list of "contributors", that would be a good spot to add your name. As it happens, we have a perfectly accurate and up to date contributor list at https://github.com/scala-js/scala-js-java-logging/graphs/contributors, where you'll clearly appear as the main contributor as soon as this PR gets merged :-)

@cquiroz cquiroz force-pushed the java-util-logging-implementation branch from 3c2ffd2 to b67c752 Compare June 10, 2016 14:07
@cquiroz
Copy link
Contributor Author

cquiroz commented Jun 10, 2016

Updated with comments from @nicolasstucki

assertNull(record.getThrown)
}


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 lines, remove one

@nicolasstucki
Copy link
Contributor

That is all.

@cquiroz
Copy link
Contributor Author

cquiroz commented Jun 10, 2016

I'm squashing my updates right away, but perhaps it is easier to review if I only commit the fixes and the squash at the end. Any preference?

@nicolasstucki
Copy link
Contributor

It is fine if you squash.

@cquiroz cquiroz force-pushed the java-util-logging-implementation branch from b67c752 to 1069234 Compare June 10, 2016 14:26
@cquiroz
Copy link
Contributor Author

cquiroz commented Jun 10, 2016

Updated with the last comments, thanks!

@nicolasstucki
Copy link
Contributor

LGTM

@nicolasstucki nicolasstucki merged commit 5867619 into scala-js:master Jun 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants