[GitHub] incubator-edgent pull request #311: [Edgent-421] link to wiki from Developme...

GitHub user dlaboss reopened a pull request: https://github.com/apache/incubator-edgent/pull/311 [Edgent-421] link to wiki from Development.md - also tweaks to better work with Eclipse's Markdown text Editor's view. You can merge this pull request into a Git repository by running:

[jira] [Created] (EDGENT-422) desensitize FileStreamsTextFileWriterTest

Dale LaBossiere created EDGENT-422: -- Summary: desensitize FileStreamsTextFileWriterTest Key: EDGENT-422 URL: https://issues.apache.org/jira/browse/EDGENT-422 Project: Edgent Issue Type:

[jira] [Created] (EDGENT-421) Add link to wiki from DEVELOPMENT.md

Dale LaBossiere created EDGENT-421: -- Summary: Add link to wiki from DEVELOPMENT.md Key: EDGENT-421 URL: https://issues.apache.org/jira/browse/EDGENT-421 Project: Edgent Issue Type: Task

Re: Understanding the snapshot and release process

I just pulled down the latest PR contents into a new clone. I get a bunch of warnings like the one below (but things work). mvn clean install [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for

Re: Blog Ideas/Edgent Use Cases

The Edgent website seems to be a good place to put this. Once it is up on the website, a blog entry can be created to announce its availability. --Kun-Lung On Thu, Jun 15, 2017 at 9:22 AM, Dale LaBossiere wrote: > I’m interested to see what sort of things folks suggest. >

Re: Blog Ideas/Edgent Use Cases

I’m interested to see what sort of things folks suggest. Will, before embarking on a series of Blog posts, perhaps you could first try to address some of the “improve our message” items identified in [1] [2] ? An another note, I want to create “An Introduction to Edgent by a Series of Small

Re: Understanding the snapshot and release process

Thx for the cleanup for Eclipse. > On Jun 15, 2017, at 7:09 AM, Christofer Dutz > wrote: > ...It seems as if some unit-tests tend to fail in random intervals. Right > now, I had 3 Travis runs without any functional changes and I got failures on > 3 different places.

Re: Understanding the snapshot and release process

Just another question … It seems as if some unit-tests tend to fail in random intervals. Right now, I had 3 Travis runs without any functional changes and I got failures on 3 different places. Is this “normal”? If yes … I think I should start identifiying the “random failers” and investigate

Re: Understanding the snapshot and release process

Your wish is my command ;-) I just installed the latest Eclipse “Neon.3” in the Developer edition (which comes with Maven support). Then I manually deleted all existing eclipse settings in the Edgent project as otherwise Eclipse would have insisted on using them instead. Also, I added them to