[TAMAYA-134] Fix javadoc issues before releasing 0.2

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.2-incubating
• Fix Version/s: 0.2-incubating

Environment

trunk
commit 225aabc4648f1d1e1936cf03b00576dbecfa42fe Author: anatole <[e-mail]>

• Assignee: John D. Ament
• Reporter: Philipp Ottlinger
• Created: 12/Jan/16 22:30
• Updated: 08/Mar/16 11:52
• Resolved: 08/Mar/16 11:52

Description

There are some Javadoc issues, that should be addressed before forging a new release. Since I'm not a committer what's the best way to do that

• github pull request?
• patch attached to this issue?

Seen during a mvn run after checkout:

[WARNING] Javadoc Warnings
[WARNING] /tmp/incubator-tamaya/modules/server/src/main/java/org/apache/tamaya/server/spi/ScopeManager.java:67: warning: no @param for target
[WARNING] public static ConfigOperator getScope(String scopeId, String target)
[WARNING] ^
[WARNING] /tmp/incubator-tamaya/modules/server/src/main/java/org/apache/tamaya/server/spi/ScopeProvider.java:38: warning: no @param for scopeId
[WARNING] ConfigOperator getScope(String scopeId);
[WARNING] ^

and many more examples.