Re: My Edgent and PLC4X Article on the Cover-Page

Nice Job! > On Mar 23, 2018, at 5:57 AM, Christofer Dutz > wrote: > > Hi, > > today I bought the magazine with my Article and was totally amazed that it > has become one of the cover-page articles :-) > > Here some images (not the article itself though) > > https://drive.google.com/open?id=

life event

All, My first day of retirement starts tomorrow! At this time it’s unclear what my level of participation in Edgent and PLC4X will become. We’ll just have to see how it goes. I’m encouraged by the synergy between Edgent and PLC4X. Chris is a great promoter and contributor so I’m optimistic

Re: 235 warnings

Apparently Eclipse’s JDT has its own built in parser as noted in https://jaxenter.com/java-8-support-in-eclipse-107723.html > On Feb 26, 2018, at 5:08 PM, Justin Mclean wrote: > > Hi, > >> I'd be inclined to do a bunch of the clean

Re: 235 warnings

ems as with Edgent here ;-) > > If the reported problems are actual problems, we should fix them and find > ways to prevent them in the future by making IntelliJ report them too. > However my trust in reports of Eclipe is not too high. Is Sonar reporting > them too? > > Chris >

Re: 235 warnings

There were many in test code but lots in non-test code too. I don’t think there are serious problems. But with all of the warnings it’s too easy to miss significant ones or add more. Changing “Use of a raw type” from warning to info drops the warnings from 235 to 85. Then changing “Unchecked

235 warnings

On the current “master” branch, Eclipse 4.6.3 (with std Error/Warning preference config) and java 1.8.0_161, Eclipse reports 235 warnings. The bulk of these seem to be Raw type and Type safety warnings. Are there plans for dealing with these? (Warning: don’t try this with Eclipse 4.7.2 and jav

Re: Eggent provider for batch reads?

s way ... so all others ... your > opinion is required here ;-) same here > > Chris > > > > Am 19.02.18, 15:30 schrieb "Dale LaBossiere" : > >Hmm… looks like this never really got sent by by my system :-( >Sending it again and then follow up on Chris

Re: Give readRequestItems a "name" property?

t needed and implicitly given by the pipeline I am plumbing > together ... > > Chris > > Am 19.02.18, 16:39 schrieb "Christofer Dutz" : > >Hi Dale, > >I agree ... we should make it mandatory. >Let's hear what the others have to sa

Re: Batch reads with JPA like annotation magic?

Doesn’t the user need access to the response code for each annotated item? I’m unclear on why a Direction is needed/desired. Is it just for “documentation" of what is possible for an item at that address? Maybe it would be checked when the annotated class is used in a Read vs Write request to

Re: Give readRequestItems a "name" property?

I think I’m generally +1 on this, though I think *optional* names may just make it harder / less predictable to use these objects. Why not just require names? This also relates to the usability of a batch request/response object, and the ability to offer a get-item-by-name accessor, instead of

Re: Eggent provider for batch reads?

Hmm… looks like this never really got sent by by my system :-( Sending it again and then follow up on Chris’s recent mail on this topic. — Dale > On Feb 5, 2018, at 6:03 PM, Dale LaBossiere wrote: > > >> On Feb 5, 2018, at 5:43 AM, Christofer Dutz >> wrote: >>

Re: Eggent provider for batch reads?

> On Feb 5, 2018, at 5:43 AM, Christofer Dutz wrote: > ... > I was also thinking about how we could make this easier. I think this is also > a general problem we probably have solve in the "normal API" too. > > While working on some Jackson Yaml parsing code, I thought that it might be > an op

Re: Eggent provider for batch reads?

When do we need it? I know the sooner the better :-) My month is a bit hectic (retirement planning, wrapping up @ IBM, taking vacation days, etc :-) I’ve got to see where the plc API is now with respect to the objects and interactions for batch reads. But I expect adding a new fn like:

Re: [DRAFT] January Podling Report PLC4X

LGTM — Dale > On Jan 30, 2018, at 5:22 AM, Christofer Dutz > wrote: > > New month, new report … here a report I whipped up … please comment on this. > ...

Re: Interest in a code-retreat architecture round, kickoff type of thing?

Sounds like a great idea/opportunity but I’ll pass. I’ll be at my own “retirement retreat” in Florida during March and April :-) — Dale > On Jan 26, 2018, at 7:30 AM, Christofer Dutz > wrote: > > I just had a look in our calendar. So far the following options would be: > (I would suggest to u

Re: Using Github and Pull Requests

> On Jan 9, 2018, at 8:07 PM, Justin Mclean wrote: > ... > With the current set up we can do both those things i.e. merge PRs and use > issue if we want. We can get the merge button on the PR's page to show up for all our committers? If so, please make it so! :-) (I already know how to merge

Re: Using Github and Pull Requests

My introduction to git was really from a pre-ASF GitHub usage context so that very common fork/PR workflow is more familiar to me :-) It’s a nice environment for collaboration. Note if PLC4X were setup to have its GitHub repo as its main repo, not this non-writeable mirror thing, merging a PR

Re: First Apache PLC4X talk at a conference :-)

Looking fwd to hearing how it went. I’m sure you’ll crush it! — Dale > On Jan 9, 2018, at 7:25 AM, Christofer Dutz wrote: > > Hi all, > > it seems that I will be having a talk about Apache PLC4X (and Apache Edgent) > at this year’s Nortec conference in Hamburg in about 2 Weeks > (http://www.

Re: Coverage reports

On the topic of coverage… The way the “integrations” are setup, they aren’t inheriting the “Fail the build” config setup in plc4j/pom.xml. Is that intentional? Should that config be pushed up into the top level pom, or duplicated in integrations/pom.xml (or individual integrations)? Also it wo

~100 warnings in Eclipse

Hi all, I know that IntelliJ is “the only” IDE :-) That said, the current state of “master” in an Eclipse dev environment yields ~100 warnings - with typical config for Java 1.8 and Errors/Warnings and it would be best to clean these up as soon as we can / is reasonable. I’ve seen mention of