[jira] [Commented] (EDGENT-448) add a new ignore item to filter .DS_Store for mac os x

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394563#comment-16394563
 ] 

ASF GitHub Bot commented on EDGENT-448:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/349


> add a new ignore item to filter .DS_Store for mac os x
> --
>
> Key: EDGENT-448
> URL: https://issues.apache.org/jira/browse/EDGENT-448
> Project: Edgent
>  Issue Type: Wish
>Reporter: vinoyang
>Priority: Trivial
>
> for the users who use max os x, when create a dir or file, it will create a 
> {code:java}
> .DS_Store{code}
> so we should add a new item to .gitignore to filter it:
> {code:java}
> # Mac os x
> *.DS_Store
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EDGENT-447) contribute a RabbitMQ connector

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394562#comment-16394562
 ] 

ASF GitHub Bot commented on EDGENT-447:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/348


> contribute a RabbitMQ connector
> ---
>
> Key: EDGENT-447
> URL: https://issues.apache.org/jira/browse/EDGENT-447
> Project: Edgent
>  Issue Type: New Feature
>  Components: Connectors
>Reporter: vinoyang
>Priority: Minor
>
> assigned to vinoyang



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EDGENT-448) add a new ignore item to filter .DS_Store for mac os x

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385000#comment-16385000
 ] 

ASF GitHub Bot commented on EDGENT-448:
---

GitHub user yanghua opened a pull request:

https://github.com/apache/incubator-edgent/pull/349

[EDGENT-448] add a new ignore item to filter .DS_Store for mac os x

## What is the purpose of the change

This PR adds a new ignore item to filter .DS_Store for mac os x.

## Brief change log

  - *Add a new ignore item to filter .DS_Store for mac os x*

## Verifying this change

This change is trivial and no test case to verify.

## Does this pull request potentially affect one of the following parts: NO

## Documentation

  - Does this pull request introduce a new feature? (no)
  - If yes, how is the feature documented? (not documented)


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

$ git pull https://github.com/yanghua/incubator-edgent EDGENT-448

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

https://github.com/apache/incubator-edgent/pull/349.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 #349


commit 1ad6614c5fd266e69d4d38f48e6083f0dd08bffb
Author: vinoyang 
Date:   2018-03-04T06:48:43Z

[EDGENT-448] add a new ignore item to filter .DS_Store for mac os x




> add a new ignore item to filter .DS_Store for mac os x
> --
>
> Key: EDGENT-448
> URL: https://issues.apache.org/jira/browse/EDGENT-448
> Project: Edgent
>  Issue Type: Wish
>Reporter: vinoyang
>Priority: Trivial
>
> for the users who use max os x, when create a dir or file, it will create a 
> {code:java}
> .DS_Store{code}
> so we should add a new item to .gitignore to filter it:
> {code:java}
> # Mac os x
> *.DS_Store
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EDGENT-447) contribute a RabbitMQ connector

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384975#comment-16384975
 ] 

ASF GitHub Bot commented on EDGENT-447:
---

GitHub user yanghua opened a pull request:

https://github.com/apache/incubator-edgent/pull/348

[EDGENT-447][Connectors] contribute a RabbitMQ connector

## What is the purpose of the change

This PR contribute a RabbitMQ connector for edgent.

## Brief change log

  - *Implement a `RabbitmqProducer` and `RabbitmqConsumer` as a source & 
sink to integrate with edgent*
  - *Implement a test case to verify the connector*

## Verifying this change

This change added tests and can be verified as follows:

  - *install & start RabbitMQ server then run 
`RabbitmqStreamsTestManual.testSimple` it will pass throgh*

## Does this pull request potentially affect one of the following parts:

  - Dependencies (does it add or upgrade a dependency): (yes)
  - The public API, i.e., is any changed : (no)
  - Anything that affects deployment: (no)

## Documentation

  - Does this pull request introduce a new feature? (yes)
  - If yes, how is the feature documented? (documented with JavaDoc)


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

$ git pull https://github.com/yanghua/incubator-edgent EDGENT-447

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

https://github.com/apache/incubator-edgent/pull/348.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 #348


commit 616f47e0304165090786ca167c57c00b8355b3d2
Author: vinoyang 
Date:   2018-03-04T05:39:25Z

[EDGENT-447][Connectors] contribute a RabbitMQ connector




> contribute a RabbitMQ connector
> ---
>
> Key: EDGENT-447
> URL: https://issues.apache.org/jira/browse/EDGENT-447
> Project: Edgent
>  Issue Type: New Feature
>  Components: Connectors
>Reporter: vinoyang
>Priority: Minor
>
> assigned to vinoyang



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (EDGENT-413) Simplify download experience

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152227#comment-16152227
 ] 

ASF GitHub Bot commented on EDGENT-413:
---

Github user johnament closed the pull request at:

https://github.com/apache/incubator-edgent/pull/307


> Simplify download experience
> 
>
> Key: EDGENT-413
> URL: https://issues.apache.org/jira/browse/EDGENT-413
> Project: Edgent
>  Issue Type: Improvement
>Reporter: John D. Ament
>
> Edgent binaries are not distributed via maven.  To simplify consumer use 
> cases, it would be better to see these binaries in a java based repository 
> manager.
> When doing this, it would also be good to remove the heavy binary 
> distribution in favor of a simpler maven staging repository with the binaries 
> in it, but it may make sense to split out that work after this is in.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EDGENT-428) Adding support for csv in MetricsSetup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114852#comment-16114852
 ] 

ASF GitHub Bot commented on EDGENT-428:
---

Github user thomascristanis commented on a diff in the pull request:

https://github.com/apache/incubator-edgent/pull/315#discussion_r131465709
  
--- Diff: 
utils/metrics/src/main/java/org/apache/edgent/metrics/MetricsSetup.java ---
@@ -111,6 +144,25 @@ private MBeanServer mbeanServer() {
 }
 return mBeanServer;
 }
+
+/**
+ * Creates a default directory for metrics.
+ * 
+ * @return directory.getPath()
+ */
+private String createDefaultDirectory() {
+Path currentRelativePath = Paths.get("");
+String pathMetrics = 
currentRelativePath.toAbsolutePath().toString() + FOLDER_METRICS;
+File directory = new File(pathMetrics);
+
+if (!directory.mkdirs()) {
+// Log: "Could not create the directory log"
--- End diff --

Great idea @dlaboss.
I'll do it as soon as possible.
All Edgent needs to improve this point, the logs.

Thanks!


> Adding support for csv in MetricsSetup
> --
>
> Key: EDGENT-428
> URL: https://issues.apache.org/jira/browse/EDGENT-428
> Project: Edgent
>  Issue Type: New Feature
>  Components: Utils
>Affects Versions: Apache Edgent 1.1.0
> Environment: Raspberry PI
>Reporter: Thomas Cristanis Cabral Nogueira
>Assignee: Dale LaBossiere
>Priority: Minor
>  Labels: features
> Fix For: Apache Edgent 1.1.0
>
> Attachments: Screen Shot 2017-07-18 at 09.34.36.png, Screen Shot 
> 2017-07-18 at 09.35.24.png, Screen Shot 2017-07-19 at 11.48.37.png
>
>
> In the current project status only had the support will JMX. So it was 
> implementing the support to generate .csv files in accordance with [metrics 
> library|http://metrics.dropwizard.io/3.1.0/manual/core/#man-core-reporters-csv]
>  already used in the project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EDGENT-428) Adding support for csv in MetricsSetup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114800#comment-16114800
 ] 

ASF GitHub Bot commented on EDGENT-428:
---

Github user dlaboss commented on a diff in the pull request:

https://github.com/apache/incubator-edgent/pull/315#discussion_r131459749
  
--- Diff: 
utils/metrics/src/main/java/org/apache/edgent/metrics/MetricsSetup.java ---
@@ -111,6 +144,25 @@ private MBeanServer mbeanServer() {
 }
 return mBeanServer;
 }
+
+/**
+ * Creates a default directory for metrics.
+ * 
+ * @return directory.getPath()
+ */
+private String createDefaultDirectory() {
+Path currentRelativePath = Paths.get("");
+String pathMetrics = 
currentRelativePath.toAbsolutePath().toString() + FOLDER_METRICS;
+File directory = new File(pathMetrics);
+
+if (!directory.mkdirs()) {
+// Log: "Could not create the directory log"
--- End diff --

I'm going to merge this now.  Thomas, when you get a chance it would be 
great to add the logging.  Thanks!


> Adding support for csv in MetricsSetup
> --
>
> Key: EDGENT-428
> URL: https://issues.apache.org/jira/browse/EDGENT-428
> Project: Edgent
>  Issue Type: New Feature
>  Components: Utils
>Affects Versions: Apache Edgent 1.1.0
> Environment: Raspberry PI
>Reporter: Thomas Cristanis Cabral Nogueira
>Assignee: Dale LaBossiere
>Priority: Minor
>  Labels: features
> Fix For: Apache Edgent 1.1.0
>
> Attachments: Screen Shot 2017-07-18 at 09.34.36.png, Screen Shot 
> 2017-07-18 at 09.35.24.png, Screen Shot 2017-07-19 at 11.48.37.png
>
>
> In the current project status only had the support will JMX. So it was 
> implementing the support to generate .csv files in accordance with [metrics 
> library|http://metrics.dropwizard.io/3.1.0/manual/core/#man-core-reporters-csv]
>  already used in the project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EDGENT-428) Adding support for csv in MetricsSetup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107362#comment-16107362
 ] 

ASF GitHub Bot commented on EDGENT-428:
---

Github user dlaboss commented on a diff in the pull request:

https://github.com/apache/incubator-edgent/pull/315#discussion_r130367741
  
--- Diff: 
utils/metrics/src/main/java/org/apache/edgent/metrics/MetricsSetup.java ---
@@ -111,6 +144,25 @@ private MBeanServer mbeanServer() {
 }
 return mBeanServer;
 }
+
+/**
+ * Creates a default directory for metrics.
+ * 
+ * @return directory.getPath()
+ */
+private String createDefaultDirectory() {
+Path currentRelativePath = Paths.get("");
+String pathMetrics = 
currentRelativePath.toAbsolutePath().toString() + FOLDER_METRICS;
+File directory = new File(pathMetrics);
+
+if (!directory.mkdirs()) {
+// Log: "Could not create the directory log"
--- End diff --

Can you fill in the logging?  Edgent uses slf4j for 
[logging](https://github.com/apache/incubator-edgent/blob/master/DEVELOPMENT.md#logging).
  Sample use of it can be seen in 
[MqttConnector.java](https://github.com/apache/incubator-edgent/blob/master/connectors/mqtt/src/main/java/org/apache/edgent/connectors/mqtt/runtime/MqttConnector.java).
  Thanks!


> Adding support for csv in MetricsSetup
> --
>
> Key: EDGENT-428
> URL: https://issues.apache.org/jira/browse/EDGENT-428
> Project: Edgent
>  Issue Type: New Feature
>  Components: Utils
>Affects Versions: Apache Edgent 1.1.0
> Environment: Raspberry PI
>Reporter: Thomas Cristanis Cabral Nogueira
>Priority: Minor
>  Labels: features
> Fix For: Apache Edgent 1.1.0
>
> Attachments: Screen Shot 2017-07-18 at 09.34.36.png, Screen Shot 
> 2017-07-18 at 09.35.24.png, Screen Shot 2017-07-19 at 11.48.37.png
>
>
> In the current project status only had the support will JMX. So it was 
> implementing the support to generate .csv files in accordance with [metrics 
> library|http://metrics.dropwizard.io/3.1.0/manual/core/#man-core-reporters-csv]
>  already used in the project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EDGENT-428) Adding support for csv in MetricsSetup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093968#comment-16093968
 ] 

ASF GitHub Bot commented on EDGENT-428:
---

GitHub user thomascristanis opened a pull request:

https://github.com/apache/incubator-edgent/pull/315

[EDGENT-428] Adding support for csv in MetricsSetup

In the current project status only had the support will JMX. So it was 
implementing the support to generate ._csv_ files in accordance with [metrics 
library](http://metrics.dropwizard.io/3.1.0/manual/core/#man-core-reporters-csv)
 already used in the project.

[[EDGENT-428] Adding support for csv in 
MetricsSetup](https://issues.apache.org/jira/browse/EDGENT-428)

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

$ git pull https://github.com/thomascristanis/incubator-edgent master

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

https://github.com/apache/incubator-edgent/pull/315.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 #315


commit fe7c3c21fbb168fd0159e8bbf8848f1beba757c6
Author: Thomas Cristanis 
Date:   2017-07-19T23:35:56Z

Implemented support for csv. Which periodically appends to a set of .csv 
files in a given directory




> Adding support for csv in MetricsSetup
> --
>
> Key: EDGENT-428
> URL: https://issues.apache.org/jira/browse/EDGENT-428
> Project: Edgent
>  Issue Type: New Feature
>  Components: Utils
>Affects Versions: Apache Edgent 1.1.0
> Environment: Raspberry PI
>Reporter: Thomas Cristanis Cabral Nogueira
>Priority: Minor
>  Labels: features
> Fix For: Apache Edgent 1.1.0
>
> Attachments: Screen Shot 2017-07-18 at 09.34.36.png, Screen Shot 
> 2017-07-18 at 09.35.24.png, Screen Shot 2017-07-19 at 11.48.37.png
>
>
> In the current project status only had the support will JMX. So it was 
> implementing the support to generate .csv files in accordance with [metrics 
> library|http://metrics.dropwizard.io/3.1.0/manual/core/#man-core-reporters-csv]
>  already used in the project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EDGENT-413) Simplify download experience

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015826#comment-16015826
 ] 

ASF GitHub Bot commented on EDGENT-413:
---

GitHub user johnament opened a pull request:

https://github.com/apache/incubator-edgent/pull/307

[EDGENT-413] Adding publishing support for ASF repos.

This is the first step for EDGENT-413.  The publishing support was mostly 
there, this adds references to the ASF managed username/password and snapshot 
URL, if we choose snapshots.  When doing a release you can now publish and it 
will create a staging repo.

To setup staging, you would need to create `~/.gradle/gradle.properties` 
and add `asfNexusUsername` and `asfNexusPassword` as properties, pointing to 
your ASF credentials.

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

$ git pull https://github.com/johnament/incubator-edgent EDGENT-413

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

https://github.com/apache/incubator-edgent/pull/307.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 #307


commit da2b545f0e5850c016a33da16148d783bc7fbc43
Author: John Ament 
Date:   2017-05-18T14:22:19Z

[EDGENT-413] Adding publishing support for ASF repos.




> Simplify download experience
> 
>
> Key: EDGENT-413
> URL: https://issues.apache.org/jira/browse/EDGENT-413
> Project: Edgent
>  Issue Type: Improvement
>Reporter: John D. Ament
>
> Edgent binaries are not distributed via maven.  To simplify consumer use 
> cases, it would be better to see these binaries in a java based repository 
> manager.
> When doing this, it would also be good to remove the heavy binary 
> distribution in favor of a simpler maven staging repository with the binaries 
> in it, but it may make sense to split out that work after this is in.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EDGENT-410) Update the Apache Incubator logo to the new logo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983256#comment-15983256
 ] 

ASF GitHub Bot commented on EDGENT-410:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/95


> Update the Apache Incubator logo to the new logo
> 
>
> Key: EDGENT-410
> URL: https://issues.apache.org/jira/browse/EDGENT-410
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>
> The Incubator has recently selected a new logo. We need to update the logo on 
> our website to use the new logo (the first image in Press Kit for Podlings 
> page at http://incubator.apache.org/guides/press-kit.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EDGENT-410) Update the Apache Incubator logo to the new logo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983255#comment-15983255
 ] 

ASF GitHub Bot commented on EDGENT-410:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/95

[EDGENT-410] Update Apache Incubator logo

Also add the footer to the rest of the site.

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

$ git pull https://github.com/queeniema/incubator-edgent-website EDGENT-410

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

https://github.com/apache/incubator-edgent-website/pull/95.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 #95






> Update the Apache Incubator logo to the new logo
> 
>
> Key: EDGENT-410
> URL: https://issues.apache.org/jira/browse/EDGENT-410
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>
> The Incubator has recently selected a new logo. We need to update the logo on 
> our website to use the new logo (the first image in Press Kit for Podlings 
> page at http://incubator.apache.org/guides/press-kit.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EDGENT-371) Not seeing animations with chrome

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849167#comment-15849167
 ] 

ASF GitHub Bot commented on EDGENT-371:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/91


> Not seeing animations with chrome
> -
>
> Key: EDGENT-371
> URL: https://issues.apache.org/jira/browse/EDGENT-371
> Project: Edgent
>  Issue Type: Bug
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
> Attachments: Screen Shot 2017-01-24 at 10.54.30 AM.png
>
>
> Using chrome (v55.0 on OSX) I navigated to 
> https://edgent.apache.org/docs/streaming-concepts.  I didn't see the 
> animations.  I noticed the protections shield shown in the screenshot 
> attachment.  Can anything be done on the site to make this all "just work"?
> Using firefox the animations on 
> https://edgent.apache.org/docs/streaming-concepts show up fine (though it 
> shows the connection as insecure and apparently I may have allowed that in 
> the past).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EDGENT-364) Update instructions on how to use the binary/source release bundles

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824842#comment-15824842
 ] 

ASF GitHub Bot commented on EDGENT-364:
---

Github user queeniema commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/90#discussion_r96332963
  
--- Diff: site/docs/edgent-getting-started.md ---
@@ -25,32 +25,43 @@ Edgent's primary API is functional where streams are 
sourced, transformed, analy
 
 ### Downloading Apache Edgent
 
-To use Edgent you need the Edgent jars. You can either download the Edgent 
source and build it or you can download a pre-built version of Edgent. See the 
[download page]({{ site.data.project.download }}).
-
-After you have the Edgent jars, you can set up your environment.
+To use Edgent, you need the Edgent JAR files, which you may obtain by 
completing the following steps.
+
+1. Locate the Edgent release you would like to use on the [downloads 
page]({{ site.data.project.download }})
+2. In the Bundles column for the desired release:
+* Click on the _Binary_ link if you simply want to use Edgent. This is 
the easiest method is to get up and running as it contains a pre-built version 
of Edgent.
+* Click on the _Source_ link if you would like access to the Edgent 
source files. If you choose this method, you must manually build Edgent 
yourself.
+3. Download the .tgz file from one of the mirror sites
+4. Unpack the downloaded file: `tar zxvf 
apache-edgent-X.X.X-incubating-XXX.tgz`
+5. Obtain the JARs
+* If you are using a binary bundle, then the Java 8 JARs are located 
in `edgent-X.X.X/java8`
+* If you are using a source bundle, build the source code:
+1. Install [Gradle](https://gradle.org/) if it is not yet installed
+2. Navigate to the unpacked directory: `cd edgent-X.X.X-src`
+3. Run `gradle` to initialize the Gradle wrapper
+4. Build the code and Javadoc: `./gradlew assemble`
+5. The Java 8 JARs are located in 
`edgent-X.X.X-src/build/distributions/java8`
 
 ### Setting up your environment
 
-Ensure that you are running a supported environment. For more information, 
see the [Edgent overview](home). This guide assumes you're running Java 8.
-
-The Edgent Java 8 JAR files are located in the `edgent/java8/lib` 
directory.
+Ensure that you are running a supported environment. For more information, 
see the [Edgent overview](home). This guide assumes you're running Java 8. The 
Edgent Java 8 JAR files are located in either the `edgent-X.X.X/java8` or 
`edgent-X.X.X-src/build/distributions/java8` directory, depending on whether 
you downloaded a binary or source bundle.
 
 1. Create a new Java project in Eclipse, and specify Java 8 as the 
execution environment JRE:
 
-
+
 
 
-2. Modify the Java build path to include all of the JAR files in the 
`edgent\java8\lib` directory:
+2. Add all of the JAR files in the `java8\lib` directory to the project's 
build path:
--- End diff --

@dlaboss, I did not know about most of the things you mentioned! Thanks for 
that Javadoc link. Adding just a provider JAR makes things super simple!


> Update instructions on how to use the binary/source release bundles
> ---
>
> Key: EDGENT-364
> URL: https://issues.apache.org/jira/browse/EDGENT-364
> Project: Edgent
>  Issue Type: Improvement
>  Components: Documentation, Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>Priority: Minor
>
> I figure this information can be updated in the [Downloading Apache 
> Edgent|http://edgent.incubator.apache.org/docs/edgent-getting-started.html#downloading-apache-edgent]
>  section of the _Getting started_ page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-234) Console: broken doc links

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824610#comment-15824610
 ] 

ASF GitHub Bot commented on EDGENT-234:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/270


> Console: broken doc links
> -
>
> Key: EDGENT-234
> URL: https://issues.apache.org/jira/browse/EDGENT-234
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>
> In doing the Edgent rename, noticed two broken doc links in the console 
> samples.  In both cases they refer to console/package-summary 
> (package-info.java) info that doesn't exist.
> See the samples.console's "Web Console Application" link on this page 
> incubator-quarks/target/docs/javadoc/overview-summary.html
> and a similar link in the Description text on this page
> incubator-quarks/target/docs/javadoc/org/apache/edgent/samples/console/package-summary.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815388#comment-15815388
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/89


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814869#comment-15814869
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user dlaboss commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/89
  
+1 thanks for straightening this out!


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812813#comment-15812813
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user dlaboss commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/89#discussion_r95242892
  
--- Diff: site/_config.yml ---
@@ -126,9 +126,9 @@ host:127.0.0.1
 sourcerepourl: https://github.com/apache/incubator-edgent
 downloadsurl: /docs/downloads
 projurl: /
-#docsurl: /javadoc/latest
+docsurl: /javadoc/latest
 # above yields things like the following when running on a "jekyll serve" 
test server
--- End diff --

woops, sorry, just noticed your jira comment that the script is run after 
the site is built hence the msgs will still show up when running "jekyll serve" 
https://issues.apache.org/jira/browse/EDGENT-327?focusedCommentId=15812317=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15812317
If that's the case maybe add some commentary to README.md (where it 
describes running "jekyll serve") so folks know its safe to ignore those 
particular error msgs?


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812711#comment-15812711
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user dlaboss commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/89#discussion_r95234993
  
--- Diff: site/_config.yml ---
@@ -126,9 +126,9 @@ host:127.0.0.1
 sourcerepourl: https://github.com/apache/incubator-edgent
 downloadsurl: /docs/downloads
 projurl: /
-#docsurl: /javadoc/latest
+docsurl: /javadoc/latest
 # above yields things like the following when running on a "jekyll serve" 
test server
--- End diff --

With your fixes these comments are no longer true so shouldn't they and the 
orig/wrong commented out docsurl should just be removed?


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812323#comment-15812323
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user ddebrunner commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/89#discussion_r95203301
  
--- Diff: build.sh ---
@@ -1,6 +1,7 @@
 set -e
 cd site
 jekyll build -d ../content_tmp
+sed -i "" "/^@import/d; s/'DejaVu Sans',//g; s/'DejaVu Sans Mono',//g; 
s/'DejaVu Serif',//g" ../content_tmp/javadoc/*/stylesheet.css
--- End diff --

Good to have a comment here as to why this (sed) is being done.


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812303#comment-15812303
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/89

[EDGENT-327] Use local Javadoc URLs

- Removed all references to the DejaVu font in `stylesheet.css` during the 
site build process
- Added a new `favicon.ico` file to the root of the site

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

$ git pull https://github.com/queeniema/incubator-edgent-website EDGENT-327

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

https://github.com/apache/incubator-edgent-website/pull/89.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 #89


commit 7080f26d0ba23b5de8ee933f5a37bb88e1123ac3
Author: Queenie Ma 
Date:   2017-01-05T19:10:51Z

[EDGENT-327] Use local Javadoc URLs




> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802629#comment-15802629
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user queeniema closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/88


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802603#comment-15802603
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user dlaboss commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/88#discussion_r94857262
  
--- Diff: site/_config.yml ---
@@ -126,9 +126,9 @@ host:127.0.0.1
 sourcerepourl: https://github.com/apache/incubator-edgent
 downloadsurl: /docs/downloads
 projurl: /
-#docsurl: /javadoc/latest
+docsurl: /javadoc/latest
 # above yields things like the following when running on a "jekyll serve" 
test server
 # [2016-12-22 15:23:31] ERROR `/favicon.ico' not found.
 # [2016-12-22 15:33:17] ERROR `/javadoc/latest/resources/fonts/dejavu.css' 
not found.
 # the following is undesirable as it doesn't link to the "jekyll serve" 
test server
-docsurl: https://edgent.incubator.apache.org/javadoc/latest
+# docsurl: https://edgent.incubator.apache.org/javadoc/latest
--- End diff --

Yeah, I thought the javadoc looked correct too but wasn't confident they 
were completely benign.  But even if benign, I think it's a bad idea to commit 
something that's generating them.  At best folks will be later be surprised / 
confused by them.


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802554#comment-15802554
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user queeniema commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/88#discussion_r94853886
  
--- Diff: site/_config.yml ---
@@ -126,9 +126,9 @@ host:127.0.0.1
 sourcerepourl: https://github.com/apache/incubator-edgent
 downloadsurl: /docs/downloads
 projurl: /
-#docsurl: /javadoc/latest
+docsurl: /javadoc/latest
 # above yields things like the following when running on a "jekyll serve" 
test server
 # [2016-12-22 15:23:31] ERROR `/favicon.ico' not found.
 # [2016-12-22 15:33:17] ERROR `/javadoc/latest/resources/fonts/dejavu.css' 
not found.
 # the following is undesirable as it doesn't link to the "jekyll serve" 
test server
-docsurl: https://edgent.incubator.apache.org/javadoc/latest
+# docsurl: https://edgent.incubator.apache.org/javadoc/latest
--- End diff --

I still see the error messages related to `dejavu.css`, but the Javadoc 
looks correct.


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802542#comment-15802542
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user queeniema commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/88#discussion_r94853271
  
--- Diff: site/_data/mydoc/mydoc_topnav.yml ---
@@ -60,24 +60,24 @@ javadoc_dropdowns:
   version: all
   output: web
   items:
-- title: lastest
-  external_url: 
http://edgent.incubator.apache.org/javadoc/latest/index.html
+- title: latest
+  url: /..\/javadoc\/latest
--- End diff --

When testing locally, Jekyll wasn't recognizing the path without the 
backslashes. Does `url: /javadoc/latest` work for anyone else?


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802490#comment-15802490
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

Github user dlaboss commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/88#discussion_r94849130
  
--- Diff: site/_data/mydoc/mydoc_topnav.yml ---
@@ -60,24 +60,24 @@ javadoc_dropdowns:
   version: all
   output: web
   items:
-- title: lastest
-  external_url: 
http://edgent.incubator.apache.org/javadoc/latest/index.html
+- title: latest
+  url: /..\/javadoc\/latest
--- End diff --

newbie question: why the backslash characters?


> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-234) Console: broken doc links

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802248#comment-15802248
 ] 

ASF GitHub Bot commented on EDGENT-234:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/270

[EDGENT-234] Remove broken Console links in the Javadoc



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

$ git pull https://github.com/queeniema/incubator-edgent EDGENT-234

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

https://github.com/apache/incubator-edgent/pull/270.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 #270


commit f8db5d450975f8190065dfc8de1d2ef5e700616c
Author: Queenie Ma 
Date:   2017-01-05T19:18:02Z

[EDGENT-234] Remove broken Console links in the Javadoc




> Console: broken doc links
> -
>
> Key: EDGENT-234
> URL: https://issues.apache.org/jira/browse/EDGENT-234
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>
> In doing the Edgent rename, noticed two broken doc links in the console 
> samples.  In both cases they refer to console/package-summary 
> (package-info.java) info that doesn't exist.
> See the samples.console's "Web Console Application" link on this page 
> incubator-quarks/target/docs/javadoc/overview-summary.html
> and a similar link in the Description text on this page
> incubator-quarks/target/docs/javadoc/org/apache/edgent/samples/console/package-summary.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802231#comment-15802231
 ] 

ASF GitHub Bot commented on EDGENT-327:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/88

[EDGENT-327] Use local Javadoc URLs



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

$ git pull https://github.com/queeniema/incubator-edgent-website EDGENT-327

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

https://github.com/apache/incubator-edgent-website/pull/88.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 #88


commit d6fa38716ec171d67e77c9cc51a00abd1cb55f51
Author: Queenie Ma 
Date:   2017-01-05T19:10:51Z

[EDGENT-327] Use local Javadoc URLs




> some http urls in the website prevent full local testing
> 
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server") 
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note 
> there about issues encountered when I tried changing it from a http url to a 
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in 
> site/_data/mydoc/mydoc_topnav.yml are http links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801986#comment-15801986
 ] 

ASF GitHub Bot commented on EDGENT-200:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/258


> Console: stream hovers in oplet kind layout lack tuple counts
> -
>
> Key: EDGENT-200
> URL: https://issues.apache.org/jira/browse/EDGENT-200
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: in_equals_out_tuple_count.png, 
> in_not_equal_to_out_tuple_count.png, stream_hover_current.png, 
> tuple_count_static_layer.png
>
>
> stream hovers lack tuple count.  oplet hovers have them.
> related, wish the stream/oplet hovers in the static layout had tuple cnt info 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15801734#comment-15801734
 ] 

ASF GitHub Bot commented on EDGENT-200:
---

Github user queeniema closed the pull request at:

https://github.com/apache/incubator-edgent/pull/258


> Console: stream hovers in oplet kind layout lack tuple counts
> -
>
> Key: EDGENT-200
> URL: https://issues.apache.org/jira/browse/EDGENT-200
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: in_equals_out_tuple_count.png, 
> in_not_equal_to_out_tuple_count.png, stream_hover_current.png, 
> tuple_count_static_layer.png
>
>
> stream hovers lack tuple count.  oplet hovers have them.
> related, wish the stream/oplet hovers in the static layout had tuple cnt info 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-322) Source function recipe missing submit()

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15771252#comment-15771252
 ] 

ASF GitHub Bot commented on EDGENT-322:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/84


> Source function recipe missing submit()
> ---
>
> Key: EDGENT-322
> URL: https://issues.apache.org/jira/browse/EDGENT-322
> Project: Edgent
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>Priority: Minor
>
> Recipe http://edgent.incubator.apache.org/recipes/recipe_source_function.html 
> can lead to confusion with newbies because the main() part way down the page 
> lacks the "dp.submit(top)" necessary for it to generate the output shown. 
> (note, it's present in the periodic section's main)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-322) Source function recipe missing submit()

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15771169#comment-15771169
 ] 

ASF GitHub Bot commented on EDGENT-322:
---

GitHub user dlaboss opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/84

[Edgent-326] website faqs, downloads cleanup

- clarify 1.0.0-incubating on sidebar of doc
- change quarks github reference to edgent
- fix stackoverflow apache-edgent tag reference
- define separate src and bin download urls for signatures, ...
- add way to navigate back to edgent home from documentation page (Edgent 
References -> ...)
- change Download Source to Downloads
- refactor the downloads page to simplify and for separate src vs bin 
signatures, etc
- tweak doap_Edgent.rdf
- simplify and correct stuff in faq
- fix source-function recipe (EDGENT-322)

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

$ git pull https://github.com/dlaboss/incubator-edgent-website 
tweakDownloads

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

https://github.com/apache/incubator-edgent-website/pull/84.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 #84


commit 13c657adc448da0cbed81e241527a99cf5f2828b
Author: Dale LaBossiere 
Date:   2016-12-22T21:26:15Z

[Edgent-326] more website cleanup

commit 951f4413c06f6c7fa135c5a47ab3db8cecbee241
Author: Dale LaBossiere 
Date:   2016-12-22T21:41:04Z

fix new External References -> edgent.apache.org link




> Source function recipe missing submit()
> ---
>
> Key: EDGENT-322
> URL: https://issues.apache.org/jira/browse/EDGENT-322
> Project: Edgent
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>Priority: Minor
>
> Recipe http://edgent.incubator.apache.org/recipes/recipe_source_function.html 
> can lead to confusion with newbies because the main() part way down the page 
> lacks the "dp.submit(top)" necessary for it to generate the output shown. 
> (note, it's present in the periodic section's main)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15770985#comment-15770985
 ] 

ASF GitHub Bot commented on EDGENT-200:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/258

[EDGENT-200] Console: Add missing tuple counts



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

$ git pull https://github.com/queeniema/incubator-edgent EDGENT-200

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

https://github.com/apache/incubator-edgent/pull/258.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 #258


commit 8b34651a3ba489dc6adad58048fe5deb0ffa0285
Author: Queenie Ma 
Date:   2016-12-22T20:09:43Z

[EDGENT-200] Console: Add missing tuple counts




> Console: stream hovers in oplet kind layout lack tuple counts
> -
>
> Key: EDGENT-200
> URL: https://issues.apache.org/jira/browse/EDGENT-200
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: in_equals_out_tuple_count.png, 
> in_not_equal_to_out_tuple_count.png, stream_hover_current.png, 
> tuple_count_static_layer.png
>
>
> stream hovers lack tuple count.  oplet hovers have them.
> related, wish the stream/oplet hovers in the static layout had tuple cnt info 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769164#comment-15769164
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/83


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769162#comment-15769162
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

GitHub user Cazen opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/83

[EDGENT-323] change some links setting



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

$ git pull https://github.com/Cazen/incubator-edgent-website EDGENT-323

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

https://github.com/apache/incubator-edgent-website/pull/83.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 #83


commit 94572384a4dda3794d7dcad37cd5670dc334d033
Author: Cazen Lee 
Date:   2016-12-22T05:57:54Z

change some links setting




> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769122#comment-15769122
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/82


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15767554#comment-15767554
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user dlaboss commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/82
  
+1 thanks!


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765636#comment-15765636
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user justinmclean commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/82#discussion_r93351844
  
--- Diff: site/docs/downloads.md ---
@@ -0,0 +1,13 @@
+---
+title: Downloads
+---
+
--- End diff --

you might also want to add a link to the KEYS and asc files so the releases 
can be verified.


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765625#comment-15765625
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user Cazen commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/82
  
@dlaboss Thank you for detailed guide.
I will reflect your requirements soon


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761517#comment-15761517
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user dlaboss commented on a diff in the pull request:


https://github.com/apache/incubator-edgent-website/pull/82#discussion_r93057962
  
--- Diff: site/docs/faq.md ---
@@ -44,7 +44,7 @@ Edgent is a tool for edge analytics that allows you to be 
more productive. Edgen
 
 ## Where can I download Apache Edgent to try it out?
 
-You can download the source from Apache and build it yourself [here]({{ 
site.data.project.source_repository_mirror }}). You can also find already 
pre-built Apache releases of Edgent for download [here]({{ 
site.data.project.apache_release_location }}) (But this location is temporarily 
unavailable until we get the first release out).
+You can download the source from Apache and build it yourself [here]({{ 
site.data.project.download }}). You can also find already pre-built Apache 
releases of Edgent for download [here]({{ 
site.data.project.apache_release_location }}) (But this location is temporarily 
unavailable until we get the first release out).
--- End diff --

I suggest simplifying this and adding all of the details to the downloads 
page. E.g., simply say "You can download Apache Edgent from --link to the 
downloads.html page--.


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761473#comment-15761473
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user dlaboss commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/82
  
[~Cazen] thanks for picking up this jira! (and your other deliveries the 
last couple of days)
I sent a clarifying note to @dev regarding the location of the release 
artifacts.  Hope that clears some things up: 
https://www.mail-archive.com/dev@edgent.apache.org/msg00933.html.

Yes, a cool page is highly desired I think. If that can be achieved in 
a day or two that would be great.  Otherwise a quick/simple first-iteration 
page will allow making the release announcement sooner and the page can be 
enhanced after the fact.


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758915#comment-15758915
 ] 

ASF GitHub Bot commented on EDGENT-323:
---

Github user Cazen commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/82
  
- I noticed that we need publish our artifacts to dist.apache.org. So 
download links will be changed after publishing.
- And I'm afraid that do we need a cool download page that includes 
design rather than a simple download page under doc(doc/download.html)?


> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-324) Change document version information from 0.3.0 to 1.0.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756962#comment-15756962
 ] 

ASF GitHub Bot commented on EDGENT-324:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/81


> Change document version information from 0.3.0 to 1.0.0
> ---
>
> Key: EDGENT-324
> URL: https://issues.apache.org/jira/browse/EDGENT-324
> Project: Edgent
>  Issue Type: Improvement
>Reporter: Cazen Lee
>Assignee: Cazen Lee
>Priority: Minor
>
> Left side version information is out of date
> (http://edgent.incubator.apache.org/docs/home)
> Will be update to 1.0.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-324) Change document version information from 0.3.0 to 1.0.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756959#comment-15756959
 ] 

ASF GitHub Bot commented on EDGENT-324:
---

GitHub user Cazen opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/81

[EDGENT-324] change Edgent version config from 0.3.0 to 1.0.0



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

$ git pull https://github.com/Cazen/incubator-edgent-website EDGENT-324

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

https://github.com/apache/incubator-edgent-website/pull/81.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 #81


commit d1822d8b397c2117c8e7607afcc6934de88cfae8
Author: Cazen Lee 
Date:   2016-12-17T12:43:58Z

change Edgent version config from 0.3.0 to 1.0.0




> Change document version information from 0.3.0 to 1.0.0
> ---
>
> Key: EDGENT-324
> URL: https://issues.apache.org/jira/browse/EDGENT-324
> Project: Edgent
>  Issue Type: Improvement
>Reporter: Cazen Lee
>Assignee: Cazen Lee
>Priority: Minor
>
> Left side version information is out of date
> (http://edgent.incubator.apache.org/docs/home)
> Will be update to 1.0.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-297) Update docs/javadoc on web site to reflect the new version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15756706#comment-15756706
 ] 

ASF GitHub Bot commented on EDGENT-297:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/79


> Update docs/javadoc on web site to reflect the new version
> --
>
> Key: EDGENT-297
> URL: https://issues.apache.org/jira/browse/EDGENT-297
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> Create & upload javadoc for the new version.
> Update the version info on https://edgent.apache.org/docs/home



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-297) Update docs/javadoc on web site to reflect the new version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754829#comment-15754829
 ] 

ASF GitHub Bot commented on EDGENT-297:
---

Github user dlaboss commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/79
  
release 1.0.0-incubating has been been approved and is available under 
https://dist.apache.org/repos/dist/release/incubator/edgent/
Please merge this ASAP so that an official announcement can be made. 
Thanks!  


> Update docs/javadoc on web site to reflect the new version
> --
>
> Key: EDGENT-297
> URL: https://issues.apache.org/jira/browse/EDGENT-297
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> Create & upload javadoc for the new version.
> Update the version info on https://edgent.apache.org/docs/home



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-289) Verify an Eclipse runtime development environment can be setup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15674789#comment-15674789
 ] 

ASF GitHub Bot commented on EDGENT-289:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/248

[EDGENT-289] Fix for DEVELOPMENT.md



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

$ git pull https://github.com/queeniema/incubator-edgent EDGENT-289

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

https://github.com/apache/incubator-edgent/pull/248.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 #248


commit 67c7f339c48da4242ec53589bf3d3382ac5ba10a
Author: Queenie Ma 
Date:   2016-11-17T20:52:21Z

[EDGENT-289] Fix for DEVELOPMENT.md




> Verify an Eclipse runtime development environment can be setup
> --
>
> Key: EDGENT-289
> URL: https://issues.apache.org/jira/browse/EDGENT-289
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-289) Verify an Eclipse runtime development environment can be setup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668298#comment-15668298
 ] 

ASF GitHub Bot commented on EDGENT-289:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/246


> Verify an Eclipse runtime development environment can be setup
> --
>
> Key: EDGENT-289
> URL: https://issues.apache.org/jira/browse/EDGENT-289
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-289) Verify an Eclipse runtime development environment can be setup

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668146#comment-15668146
 ] 

ASF GitHub Bot commented on EDGENT-289:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/246

[EDGENT-289] Update Eclipse setup instructions and misc. grammar fixes



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

$ git pull https://github.com/queeniema/incubator-edgent release1.0.0

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

https://github.com/apache/incubator-edgent/pull/246.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 #246


commit 0177bb455239afa8b28fef7db8d49ac93b25ea66
Author: Queenie Ma 
Date:   2016-11-15T20:04:44Z

[EDGENT-289] Update Eclipse setup instructions and misc. grammar fixes




> Verify an Eclipse runtime development environment can be setup
> --
>
> Key: EDGENT-289
> URL: https://issues.apache.org/jira/browse/EDGENT-289
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-292) Update CONTRIBUTORS

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667439#comment-15667439
 ] 

ASF GitHub Bot commented on EDGENT-292:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/237


> Update CONTRIBUTORS
> ---
>
> Key: EDGENT-292
> URL: https://issues.apache.org/jira/browse/EDGENT-292
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-297) Update docs/javadoc on web site to reflect the new version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15615510#comment-15615510
 ] 

ASF GitHub Bot commented on EDGENT-297:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/78


> Update docs/javadoc on web site to reflect the new version
> --
>
> Key: EDGENT-297
> URL: https://issues.apache.org/jira/browse/EDGENT-297
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-297) Update docs/javadoc on web site to reflect the new version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15602079#comment-15602079
 ] 

ASF GitHub Bot commented on EDGENT-297:
---

Github user Cazen commented on the issue:

https://github.com/apache/incubator-edgent-website/pull/78
  
I created 1.0.0 Javadoc snapshot and create a dropdown menu in 
[doc-site](http://edgent.incubator.apache.org/docs/home)(change javadoc menu to 
dropdown with lastest, 1.0.0, 0.4.0)
How does it look?


> Update docs/javadoc on web site to reflect the new version
> --
>
> Key: EDGENT-297
> URL: https://issues.apache.org/jira/browse/EDGENT-297
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556646#comment-15556646
 ] 

ASF GitHub Bot commented on EDGENT-262:
---

GitHub user home4slc opened a pull request:

https://github.com/apache/incubator-edgent/pull/217

EDGENT-262 remove console licenses

Removed all the *license* files from console/servlets/webapp_content/js/ext 
and pointed to the MIT license in servlets/LICENSE

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

$ git pull https://github.com/home4slc/incubator-edgent 
EDGENT-262_remove_licenses

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

https://github.com/apache/incubator-edgent/pull/217.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 #217


commit 16ce45df00296b886c8cb5582e265d5a5b0344a8
Author: Susan L. Cline 
Date:   2016-10-07T23:39:46Z

EDGENT-262 remove console licenses




> origin and disposition of console/servlets/webapp_content/js/ext
> 
>
> Key: EDGENT-262
> URL: https://issues.apache.org/jira/browse/EDGENT-262
> Project: Edgent
>  Issue Type: Task
>Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository 
> (EDGENT-261, EDGENT-139) I encountered 
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as 
> org.webjars:jquery-ui:1.11.4  (@ 
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such 
> luck.
> Ultimately, will we be able to remove those files from the repository and 
> download them from a maven repository to build Edgent and include in a 
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the 
> included content's license/notice info:
>console.war/{LICENSE,NOTICE}
>edgent-repository/LICENSE,NOTICE
>binary-release-{license,notice}
> looking for some guidance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-263) Add source tgz generation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552666#comment-15552666
 ] 

ASF GitHub Bot commented on EDGENT-263:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/212


> Add source tgz generation
> -
>
> Key: EDGENT-263
> URL: https://issues.apache.org/jira/browse/EDGENT-263
> Project: Edgent
>  Issue Type: Task
>  Components: Miscellaneous
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-253) [gradle] upgrade gradle wrapper to use 3.1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552535#comment-15552535
 ] 

ASF GitHub Bot commented on EDGENT-253:
---

GitHub user dlaboss opened a pull request:

https://github.com/apache/incubator-edgent/pull/212

EDGENT-253 add source tgz generation



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

$ git pull https://github.com/dlaboss/incubator-edgent edgent-263-srctgz

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

https://github.com/apache/incubator-edgent/pull/212.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 #212


commit a444936100f37001ee922d9671d78b1cb78903c6
Author: Dale LaBossiere 
Date:   2016-10-06T17:00:18Z

EDGENT-253 add source tgz generation




> [gradle] upgrade gradle wrapper to use 3.1
> --
>
> Key: EDGENT-253
> URL: https://issues.apache.org/jira/browse/EDGENT-253
> Project: Edgent
>  Issue Type: Task
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15550199#comment-15550199
 ] 

ASF GitHub Bot commented on EDGENT-200:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/211


> Console: stream hovers in oplet kind layout lack tuple counts
> -
>
> Key: EDGENT-200
> URL: https://issues.apache.org/jira/browse/EDGENT-200
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: in_equals_out_tuple_count.png, 
> in_not_equal_to_out_tuple_count.png, stream_hover_current.png, 
> tuple_count_static_layer.png
>
>
> stream hovers lack tuple count.  oplet hovers have them.
> related, wish the stream/oplet hovers in the static layout had tuple cnt info 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549477#comment-15549477
 ] 

ASF GitHub Bot commented on EDGENT-200:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/211

[WIP] [EDGENT-200] Console: Tuple count updates

- [X] Add in/out tuple counts
- [ ] Add tuple counts for the _Static flow_ layer

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

$ git pull https://github.com/queeniema/incubator-edgent EDGENT-200

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

https://github.com/apache/incubator-edgent/pull/211.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 #211


commit dae7e4c70c2ddfeb6cb765a371cdc12c1a554a5e
Author: Queenie Ma 
Date:   2016-10-05T17:45:04Z

[EDGENT-200] Console: Add in/out tuple counts




> Console: stream hovers in oplet kind layout lack tuple counts
> -
>
> Key: EDGENT-200
> URL: https://issues.apache.org/jira/browse/EDGENT-200
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: stream_hover_current.png
>
>
> stream hovers lack tuple count.  oplet hovers have them.
> related, wish the stream/oplet hovers in the static layout had tuple cnt info 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-257) samples.scenarios.iotp no longer functional

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536619#comment-15536619
 ] 

ASF GitHub Bot commented on EDGENT-257:
---

Github user dlaboss closed the pull request at:

https://github.com/apache/incubator-edgent/pull/203


> samples.scenarios.iotp no longer functional
> ---
>
> Key: EDGENT-257
> URL: https://issues.apache.org/jira/browse/EDGENT-257
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>Priority: Minor
>
> samples/scenarios/iotp/range/sensor/README is inaccurate in light of using a 
> gradle tooling generated build as well as an older "iotf" => "iotp" rename.
> samples/.classpath also needs tweaking now that the sample is always built 
> and the build now includes Pi4J.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-245) replace the favicon.png for the console with a new one that uses E instead of Q

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503838#comment-15503838
 ] 

ASF GitHub Bot commented on EDGENT-245:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent/pull/192


> replace the favicon.png for the console with a new one that uses E instead of 
> Q
> ---
>
> Key: EDGENT-245
> URL: https://issues.apache.org/jira/browse/EDGENT-245
> Project: Edgent
>  Issue Type: Task
>  Components: Console
>Reporter: Susan L. Cline
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
>
> The old favicon.png has a 'Q' in the middle of it.  It needs to have the 'E' 
> in the middle of it now that the project has changed from 'Quarks' to 
> 'Edgent'.  This would be a great newbie item.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-46) Update Getting Started page to either make clear Download is not Apache or include Apache build instructions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456439#comment-15456439
 ] 

ASF GitHub Bot commented on EDGENT-46:
--

Github user cmdx closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/64


> Update Getting Started page to either make clear Download is not Apache or 
> include Apache build instructions
> 
>
> Key: EDGENT-46
> URL: https://issues.apache.org/jira/browse/EDGENT-46
> Project: Edgent
>  Issue Type: Improvement
>  Components: Documentation, Web Site
>Reporter: Kathey Marsden
>Assignee: Julia Bamford
>
> Since we don't have an Apache release yet, the Getting Started page should 
> either make it clear that the download is not an Apache release or include 
> instructions on building from source.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-233) Website: Rename Quarks to Edgent

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418127#comment-15418127
 ] 

ASF GitHub Bot commented on EDGENT-233:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/73

[EDGENT-233] More link updates



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

$ git pull https://github.com/queeniema/incubator-edgent-website EDGENT-233

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

https://github.com/apache/incubator-edgent-website/pull/73.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 #73


commit 2718125676dc45f01b470955dfd4e307be3dbfe2
Author: qfma 
Date:   2016-08-11T23:37:50Z

[EDGENT-233] More link updates




> Website: Rename Quarks to Edgent
> 
>
> Key: EDGENT-233
> URL: https://issues.apache.org/jira/browse/EDGENT-233
> Project: Edgent
>  Issue Type: Task
>  Components: Web Site
>Reporter: Queenie Ma
>Assignee: Queenie Ma
>
> References to Quarks in:
> * Text
> * Images
> * Logo(s)
> Dependencies:
> * New website URL
> * New Git/GitHub URLs
> * New JIRA URL
> * New mailing list URLs
> * New Wiki
> * New Javadoc URL/content



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)