Officially cancelling the VOTE for 1.0.0-rc1. I'll create a 1.0.0-rc2 and
start a new VOTE once the issue is resolved.
VOTE thread:
https://lists.apache.org/thread/f5qopxc7opv4z1jql8f1rq4qj5gjys32
Thank you,
Shane Dell
Ah, very much could be stale stuff from prior testing before. I only made
note of it since the wiki page instructions or readme of the project
directed me to look there. I was actually trying to figure out how to
redirect it at a different daffodil release, but put off that to test
exactly what was
Also the file path from the previous file is what will be extracted to that
~/.local/share/daffodil/ so it would have the proper the version should be the
exact name of the zip file just without zip. I believe the file you saw is from
you testing the extension locally possibly through a VSIX you
Mike,
That folder path only gets created from debugging/running the extension
locally. When installed onto a machine it will be in a different location. With
this release VSIX installed the location is for the server is:
~/.vscode/extensions/asf.apache-daffodil-vscode-1.0.0/server/core/target/un
Hmmm. Ticket https://github.com/apache/daffodil-vscode/issues/66 is closed,
so I expected breakpoints in different files of a multi-file schema should
work so long as they're all part of the same schema project/tree, i.e., not
in jar/classpath schemas.
I opened up the EDIFACT DFDL schema project (
Hello all,
I'd like to call a vote to release Apache Daffodil VS Code 1.0.0-rc1.
All distribution packages, including signatures, digests, etc. can be
found at:
https://dist.apache.org/repos/dist/dev/daffodil/daffodil-vscode/1.0.0-rc1/
This release has been signed with PGP key
86DDE7B41291E3802
