You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Philipp Ottlinger (JIRA)" <ji...@apache.org> on 2016/01/12 23:30:39 UTC
[jira] [Created] (TAMAYA-134) Fix javadoc issues before releasing
0.2
Philipp Ottlinger created TAMAYA-134:
----------------------------------------
Summary: 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 <an...@apache.org>
Reporter: Philipp Ottlinger
Priority: Minor
Fix For: 0.2-incubating
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)
Re: [jira] [Created] (TAMAYA-134) Fix javadoc issues before releasing
0.2
Posted by "P. Ottlinger" <po...@apache.org>.
Hi Anatole, fellow devs,
Am 13.01.2016 um 00:43 schrieb Anatole Tresch:
> Yes, you can attach the diff to the jira ;)
> Btw if you have any further feedback, be it good or bad, let us know. And
> if you think on helping us also as a committer you would be very welcome.
Thanks for the offer - I'd like to help out, although I'm merely
interested at the moment following your articles in German JavaMagazin.
I'm going to attach smaller patch files to the issue since I plan to do
things incrementally.
Cheers,
Phil
Re: [jira] [Created] (TAMAYA-134) Fix javadoc issues before releasing 0.2
Posted by Anatole Tresch <at...@gmail.com>.
Hi Philipp
Yes, you can attach the diff to the jira ;)
Btw if you have any further feedback, be it good or bad, let us know. And
if you think on helping us also as a committer you would be very welcome.
Best
Anatole
Am 12.01.2016 23:30 schrieb "Philipp Ottlinger (JIRA)" <ji...@apache.org>:
> Philipp Ottlinger created TAMAYA-134:
> ----------------------------------------
>
> Summary: 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 <an...@apache.org>
> Reporter: Philipp Ottlinger
> Priority: Minor
> Fix For: 0.2-incubating
>
>
> 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)
>