martint / martint/jmxutils

Source files without license headers

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
176
Forks
51
PR merge metrics
No merged PRs in 30d

Description

Hi,
The following source files are without license headers:

./src/main/java/org/weakref/jmx/JmxException.java
./src/main/java/org/weakref/jmx/ManagedAnnotation.java
./src/main/java/org/weakref/jmx/ObjectNameBuilder.java
./src/main/java/org/weakref/jmx/ObjectNames.java
./src/main/java/org/weakref/jmx/guice/ExportBinder.java
./src/main/java/org/weakref/jmx/guice/ExportBuilder.java
./src/main/java/org/weakref/jmx/guice/MapExportBinder.java
./src/main/java/org/weakref/jmx/guice/MapMapping.java
./src/main/java/org/weakref/jmx/guice/MapNamingFunction.java
./src/main/java/org/weakref/jmx/guice/MapObjectNameFunction.java
./src/main/java/org/weakref/jmx/guice/NamingFunction.java
./src/main/java/org/weakref/jmx/guice/ObjectNameFunction.java
./src/main/java/org/weakref/jmx/guice/SetExportBinder.java
./src/main/java/org/weakref/jmx/guice/SetMapping.java
./src/main/java/org/weakref/jmx/guice/StringMapExportBinder.java
./src/main/java/org/weakref/jmx/testing/TestingMBeanModule.java
./src/main/java/org/weakref/jmx/testing/TestingMBeanServer.java

./src/test/java/org/weakref/jmx/AbstractMbeanTest.java
./src/test/java/org/weakref/jmx/CustomAnnotationObject.java
./src/test/java/org/weakref/jmx/TestExports.java
./src/test/java/org/weakref/jmx/TestMBeanBuilder.java
./src/test/java/org/weakref/jmx/TestObjectNameBuilder.java
./src/test/java/org/weakref/jmx/TestObjectNames.java
./src/test/java/org/weakref/jmx/TestUnexporter.java

Please, confirm the licensing of code and/or content/s, and add license headers
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Clarification

Thanks in advance
Regards

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the listed files under src/main/java and src/test/java, then consult the linked Fedora licensing guidelines to confirm the applicable license. Add the confirmed license headers to every listed source file; the work is done when all named files contain consistent headers.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.