[
https://issues.apache.org/jira/browse/TAMAYA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Ottlinger updated TAMAYA-134:
-------------------------------------
Attachment: 20160118secondBatch_TAMAYA134.diff
Next batch of exchanges (manually removed changes to gitignore that are part of
the other diff file from 20160116).
* Fixed typos and javadoc warnings.
> Fix javadoc issues before releasing 0.2
> ---------------------------------------
>
> Key: TAMAYA-134
> URL: https://issues.apache.org/jira/browse/TAMAYA-134
> Project: Tamaya
> Issue Type: Bug
> Affects Versions: 0.2-incubating
> Environment: trunk
> commit 225aabc4648f1d1e1936cf03b00576dbecfa42fe
> Author: anatole <anat...@apache.org>
> Reporter: Philipp Ottlinger
> Priority: Minor
> Fix For: 0.2-incubating
>
> Attachments: 20160114firstBatch_TAMAYA134.diff,
> 20160116enhanceGitignore.diff, 20160118secondBatch_TAMAYA134.diff
>
>
> 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:
> {code}
> [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] ^
> {code}
> and many more examples.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
