date:20170105

Re: Edgent website analytics

2017-01-05 Thread William Marshall

Thanks Justin & Dan.

We could potentially proceed as follows


   - Create an Edgent Google Analytics account, e.g. apacheedg...@gmail.com
   - Set up Analytics using Edgent account
   - Post the account info to the PPMC



   -  Publish the monthly reports publicly.



On Thu, Jan 5, 2017 at 1:58 PM, Justin Mclean 
wrote:

> Hi,
>
> > I'd like to have a discussion about:
> > A) Should we include analytics on our site?
>
> You can if you want to, a number of other Apache projects do so.
>
> > B) On what account should the data be stored, and how should access be
> > controlled?
>
> I would post the credentials to the private list to let the PPMC manage it.
>
> > C) Are there more general concerns? Dan brought up that both Apex and
> > Apache include privacy disclaimers and linked to this JIRA:
> > https://issues.apache.org/jira/browse/APEXCORE-553
>
> Yes add a privacy policy, here’s another example [1].
>
> Thanks,
> Justin
>
> 1. http://flex.apache.org/about-privacy.html

[GitHub] incubator-edgent pull request #271: [Edgent-363] clarify / disallow null.

2017-01-05 Thread dlaboss

GitHub user dlaboss opened a pull request:

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

[Edgent-363] clarify / disallow null topology name



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

$ git pull https://github.com/dlaboss/incubator-edgent 
edgent363-nullTopoNames

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

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






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

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

2017-01-05 Thread Queenie Ma (JIRA)


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

Queenie Ma commented on EDGENT-327:
---

I looked into the {{ERROR `/javadoc/latest/resources/fonts/dejavu.css' not 
found}} messages. It seems to be a bug in the Javadoc tool due to a dangling 
reference to dejavu.css in stylesheet.css. Note the {{@import}} statement 
below. 

{code:title=stylesheet.css|borderStyle=solid}
@import url('resources/fonts/dejavu.css');

body {
background-color:#ff;
color:#353833;
font-family:'DejaVu Sans', Arial, Helvetica, sans-serif;
font-size:14px;
margin:0;
}
...
{code}

Found this related issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=470739. 
A person who commented on that issue submitted a Java bug, but it seems that 
the bug hasn't been fixed.

Workarounds are:
# Manually add the dejavu.css font file to the generated Javadoc (not sure 
where to get that file)
# Remove the {{@import}} statement and use a different default font

Thoughts?

> 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] [Created] (EDGENT-363) clarify / disallow null topology names

2017-01-05 Thread Dale LaBossiere (JIRA)

Dale LaBossiere created EDGENT-363:
--

 Summary: clarify / disallow null topology names
 Key: EDGENT-363
 URL: https://issues.apache.org/jira/browse/EDGENT-363
 Project: Edgent
  Issue Type: Bug
  Components: API
Reporter: Dale LaBossiere
Assignee: Dale LaBossiere


TopologyProvider.newTopology(String name) doesn't state that null/empty names 
are disallowed.  DirectProvider allows them.  But other places in the code will 
be unhappy or non-sensical if they are - e.g., Etaio's synthesis of a job-name.
ApplicationService.registerTopology() and IotProvider.registerTopology() are 
other places.



--
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

2017-01-05 Thread 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

2017-01-05 Thread 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

2017-01-05 Thread 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

2017-01-05 Thread 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)

[GitHub] incubator-edgent-website pull request #88: [EDGENT-327] Use local Javadoc UR...

2017-01-05 Thread queeniema

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?


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

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

2017-01-05 Thread 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)

[GitHub] incubator-edgent-website pull request #88: [EDGENT-327] Use local Javadoc UR...

2017-01-05 Thread dlaboss

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?


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

Re: Edgent website analytics

2017-01-05 Thread Dan Debrunner


On 1/5/2017 12:11 PM, Dan Debrunner wrote:


I'm not sure about how access to the data should be resolved. Does it
matter if it's open to everyone?


Jackrabbit seemed to have an automated script for a while that made the 
reports openly available:


https://jackrabbit.apache.org/analytics/

Dan.

Re: Edgent website analytics

2017-01-05 Thread Dan Debrunner


On 1/5/2017 11:57 AM, William Marshall wrote:


I'd like to have a discussion about:
A) Should we include analytics on our site?
B) On what account should the data be stored, and how should access be
controlled?
C) Are there more general concerns? Dan brought up that both Apex and
Apache include privacy disclaimers and linked to this JIRA:
https://issues.apache.org/jira/browse/APEXCORE-553


Seems many Apache projects have Google Analytics and they all seem to 
have a 'privacy-policy.html' at the root of their site.


I couldn't find any general guidance on the topic.

I'm +1 to adding Google Analytics with a privacy policy statement.

I'm not sure about how access to the data should be resolved. Does it 
matter if it's open to everyone?


Dan.

Edgent website analytics

2017-01-05 Thread William Marshall

Hi All,

In the interest of learning more about how users interact with the Edgent
site, I added a google analytics snippet to our landing and documentation
pages. This was hasty, and should have been discussed on the mailing list
first, so I have since backed out the changes.

I'd like to have a discussion about:
A) Should we include analytics on our site?
B) On what account should the data be stored, and how should access be
controlled?
C) Are there more general concerns? Dan brought up that both Apex and
Apache include privacy disclaimers and linked to this JIRA:
https://issues.apache.org/jira/browse/APEXCORE-553

It should have been discussed here first, and I apologize for committing
the changes without consulting the mailing list.

-Will

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

2017-01-05 Thread 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-234) Console: broken doc links

2017-01-05 Thread Queenie Ma (JIRA)


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

Queenie Ma commented on EDGENT-234:
---

Will remove these broken links.

> 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] [Assigned] (EDGENT-234) Console: broken doc links

2017-01-05 Thread Queenie Ma (JIRA)


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

Queenie Ma reassigned EDGENT-234:
-

Assignee: Queenie Ma

> 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

2017-01-05 Thread 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)

[GitHub] incubator-edgent-website pull request #88: [EDGENT-327] Use local Javadoc UR...

2017-01-05 Thread queeniema

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




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

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

2017-01-05 Thread Queenie Ma (JIRA)


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

Queenie Ma reassigned EDGENT-327:
-

Assignee: Queenie Ma

> 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

2017-01-05 Thread 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)

[GitHub] incubator-edgent pull request #258: [EDGENT-200] Console: Add missing tuple ...

2017-01-05 Thread asfgit

Github user asfgit closed the pull request at:

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


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

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

2017-01-05 Thread 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)

[GitHub] incubator-edgent pull request #258: [EDGENT-200] Console: Add missing tuple ...

2017-01-05 Thread queeniema

Github user queeniema closed the pull request at:

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


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

Re: Edgent website analytics

[GitHub] incubator-edgent pull request #271: [Edgent-363] clarify / disallow null.

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

[jira] [Created] (EDGENT-363) clarify / disallow null topology names

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

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

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

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

[GitHub] incubator-edgent-website pull request #88: [EDGENT-327] Use local Javadoc UR...

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

[GitHub] incubator-edgent-website pull request #88: [EDGENT-327] Use local Javadoc UR...

Re: Edgent website analytics

Re: Edgent website analytics

Edgent website analytics

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

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

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

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

[GitHub] incubator-edgent-website pull request #88: [EDGENT-327] Use local Javadoc UR...

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

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

[GitHub] incubator-edgent pull request #258: [EDGENT-200] Console: Add missing tuple ...

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

[GitHub] incubator-edgent pull request #258: [EDGENT-200] Console: Add missing tuple ...

24 matches

Site Navigation

Mail list logo

Footer information