Re: Trying register an application via the registerJar command

Many thanks, Dale. Still trying to figure this out … Cheers, Susan > On Sep 19, 2016, at 8:30 AM, Dale LaBossiere wrote: > > FYI I just created https://issues.apache.org/jira/browse/EDGENT-250 > to update IotProvider

[jira] [Comment Edited] (EDGENT-179) console: oplet coloring gradients "too close"

[ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504264#comment-15504264 ] Dale LaBossiere edited comment on EDGENT-179 at 9/19/16 6:47 PM: - The

[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"

[ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504264#comment-15504264 ] Dale LaBossiere commented on EDGENT-179: The general problem still seems to exist. Since this jira

[jira] [Updated] (EDGENT-179) console: oplet coloring gradients "too close"

[ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma updated EDGENT-179: -- Attachment: EDGENT-179_oplet_colors.png > console: oplet coloring gradients "too close" >

[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"

[ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504099#comment-15504099 ] Queenie Ma commented on EDGENT-179: --- It looks like this may have been fixed in [PR

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

[ https://issues.apache.org/jira/browse/EDGENT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma closed EDGENT-245. - Resolution: Resolved > replace the favicon.png for the console with a new one that uses E instead of > Q

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

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

[GitHub] incubator-edgent pull request #192: [EDGENT-245] Console: Update Apache Edge...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/192 --- 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

Re: Trying register an application via the registerJar command

FYI I just created https://issues.apache.org/jira/browse/EDGENT-250 to update IotProvider doc related to registerJar(). You should consider adding commentary there as part of your experiences — and/or consider tacking that jira and maybe even

[jira] [Created] (EDGENT-250) update IotProvider control service commands doc

Dale LaBossiere created EDGENT-250: -- Summary: update IotProvider control service commands doc Key: EDGENT-250 URL: https://issues.apache.org/jira/browse/EDGENT-250 Project: Edgent Issue

Re: Trying register an application via the registerJar command

The TopologyBuilder.getBuilder() impl is bogus. Looks like it’s copied from TestApplication(). All it does is return a builder (BiConsumer) that creates a topology consisting of a TStream containing one tuple with the app’s name and prints that stream. Your getBuilder() impl needs to return

[GitHub] incubator-edgent pull request #190: Edgent-240 [gradle] Overhaul dependency ...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/190 --- 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