[jira] [Resolved] (DAFFODIL-2054) Change coerecion errors to warnings and eventually deprecate

[ https://issues.apache.org/jira/browse/DAFFODIL-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence resolved DAFFODIL-2054. -- Resolution: Fixed Fixed in commit 69f399983f45cc6f878a2739698f338f8674992d >

[jira] [Commented] (DAFFODIL-2025) Remove OracleJDK7 from TravisCI

[ https://issues.apache.org/jira/browse/DAFFODIL-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745423#comment-16745423 ] Steve Lawrence commented on DAFFODIL-2025: -- Readme updated to Java 8 in commit 

[GitHub] stevedlawrence merged pull request #166: Change expression result type coercion to be a warning

stevedlawrence merged pull request #166: Change expression result type coercion to be a warning URL: https://github.com/apache/incubator-daffodil/pull/166 This is an automated message from the Apache Git Service. To respond

[jira] [Resolved] (DAFFODIL-2045) Performance degredation with hexBinary

[ https://issues.apache.org/jira/browse/DAFFODIL-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence resolved DAFFODIL-2045. -- Resolution: Fixed Fixed in commit 69bb0a185ef320acf31739d8b90e63b9f7c8a8de >

Re: First success with modeling the message formats for the Siemens S7 Protocol with Daffodil

To add on to that, the following can be used to generate a new dfdl project layout using a template: sbt new stevedlawrence/dfdl-project-layout.g8 It asks a couple questions about your format, then generates a project with skeleton files for the schema, TDML file, and scala test file. You can

Re: First success with modeling the message formats for the Siemens S7 Protocol with Daffodil

Thanks for both your responses :-) As we are building with Java and Maven, I'll probably stick more to the maven defaults and project setup. I bet there is a way to run all of these tests in Maven surefire. Has this been done before? Chris Am 17.01.19, 16:03 schrieb "Steve Lawrence" :

[GitHub] stevedlawrence commented on a change in pull request #167: Daffodil 2051 tests broken in windows

stevedlawrence commented on a change in pull request #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#discussion_r248675800 ## File path: daffodil-test/src/test/resources/org/apache/daffodil/section06/namespaces/namespaces.tdml

[GitHub] mbeckerle commented on issue #167: Daffodil 2051 tests broken in windows

mbeckerle commented on issue #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#issuecomment-455183662 The travis CI build failed due to rat check failure - a file was introduced that needs an apache license banner I believe.

First success with modeling the message formats for the Siemens S7 Protocol with Daffodil

Hi all, I just wanted to report that after finishing a first version of my S7 dfdl, I pretty quickly finished the 2 underlying protocols too. https://github.com/apache/incubator-plc4x/tree/develop/src/main/dfdl Next I will probably start with using daffodil for parsing/serializing test-data

Re: First success with modeling the message formats for the Siemens S7 Protocol with Daffodil

Very nice schema Christofer. I recommend adding tests in TDML so as to exercise these in your ordinary unit test/regression using Daffodil. This article: https://daffodil.apache.org/dfdl-layout/ explains the way we do this for sbt. Minor adaptations needed for maven I'm sure. ...mike

[GitHub] stevedlawrence commented on a change in pull request #167: Daffodil 2051 tests broken in windows

stevedlawrence commented on a change in pull request #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#discussion_r248674418 ## File path: daffodil-test-ibm1/src/test/resources/test-suite/tresys-contributed/AG.tdml ##

[GitHub] mbeckerle commented on a change in pull request #167: Daffodil 2051 tests broken in windows

mbeckerle commented on a change in pull request #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#discussion_r248491876 ## File path: daffodil-test/src/test/resources/org/apache/daffodil/section06/namespaces/namespaces.tdml

[GitHub] mbeckerle commented on a change in pull request #167: Daffodil 2051 tests broken in windows

mbeckerle commented on a change in pull request #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#discussion_r248681966 ## File path: daffodil-test/src/test/resources/org/apache/daffodil/section06/namespaces/namespaces.tdml

[GitHub] stevedlawrence commented on issue #167: Daffodil 2051 tests broken in windows

stevedlawrence commented on issue #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#issuecomment-455184370 That rat failure was introduced in commit 912f7d2b73 and we missed it. It was then fixed as part of the next commit 69bb0a185e,

[GitHub] stevedlawrence commented on issue #167: Daffodil 2051 tests broken in windows

stevedlawrence commented on issue #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#issuecomment-455186678 Also, apparently TravisCI now supports windows: https://blog.travis-ci.com/2018-10-11-windows-early-release It might

[GitHub] stevedlawrence commented on issue #167: Daffodil 2051 tests broken in windows

stevedlawrence commented on issue #167: Daffodil 2051 tests broken in windows URL: https://github.com/apache/incubator-daffodil/pull/167#issuecomment-455187436 Actually, it looking more closing, TravisCI does not support java/scala yet, so we'll have to hold off on that.

[jira] [Created] (DAFFODIL-2055) TDML Page - typographical error

Michael Beckerle created DAFFODIL-2055: -- Summary: TDML Page - typographical error Key: DAFFODIL-2055 URL: https://issues.apache.org/jira/browse/DAFFODIL-2055 Project: Daffodil Issue

Re: First success with modeling the message formats for the Siemens S7 Protocol with Daffodil

I don't know that it has been done before, but these are standard junit tests, just implemented in scala (usually), and so things that run Junit 4 tests detected in a src/test/scala or src/test/java directory will find these and run them. From: Christofer Dutz