Re: Javadoc

[Jeremy Dyer]

my apologizes the command should be "mvn javadoc:aggregate" instead of "mvn
javadoc:generate"

On Sun, Jan 17, 2016 at 3:18 PM, Jeremy Dyer  wrote:

> Devin I'm not sure of the presence of the javadocs on nifi.apache.org but
> assuming your on a linux/os x machine with git, java, and maven already
> installed the quickest way to get the latest javadocs would be the run "git
> clone https://github.com/apache/nifi.git && cd nifi && mvn
> javadoc:generate". This should generate the javadocs in
> nifi/target/site/apidocs. Hope this helps.
>
> On Sun, Jan 17, 2016 at 2:38 PM, Devin Fisher <
> devin.fis...@perfectsearchcorp.com> wrote:
>
>> Might be a silly question but I can't find a link the Javadocs anywhere on
>> your website. I've googled for it and only find the reference to the
>> Javadocs in the NiFi Developer’s Guide
>> . I'm hopeful that I'm just
>> not seeing it. If not, what is the recommended way to get a hold of it?
>>
>> Also, thanks in advanced.
>>
>> Devin
>>
>
>

Javadoc

[Devin Fisher]

Might be a silly question but I can't find a link the Javadocs anywhere on
your website. I've googled for it and only find the reference to the
Javadocs in the NiFi Developer’s Guide
. I'm hopeful that I'm just
not seeing it. If not, what is the recommended way to get a hold of it?

Also, thanks in advanced.

Devin

Re: Javadoc

[Jeremy Dyer]

Devin I'm not sure of the presence of the javadocs on nifi.apache.org but
assuming your on a linux/os x machine with git, java, and maven already
installed the quickest way to get the latest javadocs would be the run "git
clone https://github.com/apache/nifi.git && cd nifi && mvn
javadoc:generate". This should generate the javadocs in
nifi/target/site/apidocs. Hope this helps.

On Sun, Jan 17, 2016 at 2:38 PM, Devin Fisher <
devin.fis...@perfectsearchcorp.com> wrote:

> Might be a silly question but I can't find a link the Javadocs anywhere on
> your website. I've googled for it and only find the reference to the
> Javadocs in the NiFi Developer’s Guide
> . I'm hopeful that I'm just
> not seeing it. If not, what is the recommended way to get a hold of it?
>
> Also, thanks in advanced.
>
> Devin
>

?????? Javadoc

[????????????]

why not to use doxygen  to generate java docs




--  --
??: "Jeremy Dyer"; 
: 2016??1??18??(??) 4:20
??: "dev"; 
: Re: Javadoc



my apologizes the command should be "mvn javadoc:aggregate" instead of "mvn
javadoc:generate"

On Sun, Jan 17, 2016 at 3:18 PM, Jeremy Dyer  wrote:

> Devin I'm not sure of the presence of the javadocs on nifi.apache.org but
> assuming your on a linux/os x machine with git, java, and maven already
> installed the quickest way to get the latest javadocs would be the run "git
> clone https://github.com/apache/nifi.git && cd nifi && mvn
> javadoc:generate". This should generate the javadocs in
> nifi/target/site/apidocs. Hope this helps.
>
> On Sun, Jan 17, 2016 at 2:38 PM, Devin Fisher <
> devin.fis...@perfectsearchcorp.com> wrote:
>
>> Might be a silly question but I can't find a link the Javadocs anywhere on
>> your website. I've googled for it and only find the reference to the
>> Javadocs in the NiFi Developer??s Guide
>> . I'm hopeful that I'm just
>> not seeing it. If not, what is the recommended way to get a hold of it?
>>
>> Also, thanks in advanced.
>>
>> Devin
>>
>
>

Re: Javadoc

[Joe Witt]

Also of note the javadoc archives, just as is the case with source
archives, are published to Nexus which enables easy IDE integration.

Thanks
Joe

On Sun, Jan 17, 2016 at 8:35 PM, 满满的回忆杀  wrote:
> why not to use doxygen  to generate java docs
>
>
>
>
> -- 原始邮件 --
> 发件人: "Jeremy Dyer";
> 发送时间: 2016年1月18日(星期一) 凌晨4:20
> 收件人: "dev";
> 主题: Re: Javadoc
>
>
>
> my apologizes the command should be "mvn javadoc:aggregate" instead of "mvn
> javadoc:generate"
>
> On Sun, Jan 17, 2016 at 3:18 PM, Jeremy Dyer  wrote:
>
>> Devin I'm not sure of the presence of the javadocs on nifi.apache.org but
>> assuming your on a linux/os x machine with git, java, and maven already
>> installed the quickest way to get the latest javadocs would be the run "git
>> clone https://github.com/apache/nifi.git && cd nifi && mvn
>> javadoc:generate". This should generate the javadocs in
>> nifi/target/site/apidocs. Hope this helps.
>>
>> On Sun, Jan 17, 2016 at 2:38 PM, Devin Fisher <
>> devin.fis...@perfectsearchcorp.com> wrote:
>>
>>> Might be a silly question but I can't find a link the Javadocs anywhere on
>>> your website. I've googled for it and only find the reference to the
>>> Javadocs in the NiFi Developer’s Guide
>>> . I'm hopeful that I'm just
>>> not seeing it. If not, what is the recommended way to get a hold of it?
>>>
>>> Also, thanks in advanced.
>>>
>>> Devin
>>>
>>
>>

[GitHub] nifi pull request: NIFI-1406 Collecting the number of bytes sent r...

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi/pull/176

NIFI-1406 Collecting the number of bytes sent regardless of send type

Providing counting of all bytes sent to remove bug where PostHTTP would not 
have non-zero rate if not configured to send as a FlowFile.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apiri/incubator-nifi nifi-1406

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/176.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #176


commit dc8893e5d20c6a861c1002e53739e30b1e4c2386
Author: Aldrin Piri 
Date:   2016-01-18T03:14:17Z

NIFI-1406 Collecting the number of bytes sent regardless if one or multiple 
FlowFiles are sent.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1393 Providing the ability to send using g...

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi/pull/175

NIFI-1393 Providing the ability to send using gzip Content-Encoding

NIFI-1393 Providing the ability to send using gzip Content-Encoding in 
PostHTTP if the endpoint server supports it regardless if the processor is 
configured to send as a FlowFile

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apiri/incubator-nifi nifi-1393

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/175.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #175


commit 4b2776408942c6eb2571209081b7c845f5262cd8
Author: Aldrin Piri 
Date:   2016-01-14T18:24:20Z

NIFI-1393 Providing the ability to send using gzip Content-Encoding if the 
endpoint server supports it regardless if it is sent as FlowFile




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---