You may also want to issue the
sbt publishLocal command, which populates the ~/.ivy2 cache (used by sbt itself) with a local copy of the snapshot. If you use the standard schema project layout, then this lets you type sbt test in your schema directory and it will run any test defined in that schema's src/test/scala or src/test/java directory. Do demonstrate this, I have pushed a branch named for-daffodil-2.2.0 to the DFDLSchemas repository on github. So if you clone the CSV schemas with git: cd schemas # to where you keep your schema projects git clone [email protected]:DFDLSchemas/CSV.git cd CSV git checkout for-daffodil-2.2.0 # branch has build.sbt setup for daffodil 2.2.0-SNAPSHOT sbt test That will run the CSV tests against the snapshot you have locally. A good check that everything is working as expected. There may be some sbt magic to tell sbt to look in the m2 cache maven uses as well as the ivy cache. That would eliminate the sbt publishLocal step, but I'm not sure the magic incantation. -mike beckerle Tresys ________________________________ From: Jim Welch <[email protected]> Sent: Thursday, August 9, 2018 9:18:37 AM To: [email protected] Subject: Re: 2.2.0-snapshot Thanks, I am also considering updating flowervase to the current Daffodil,
