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 distributed.
On Thu, Mar 3, 2022 at 2:46 PM Shane Dell <shaned...@apache.org> wrote: > 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 made yourself or just debugging it via vscode. > > > On 2022/03/03 19:41:25 Shane Dell wrote: > > 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/universal/daffodil-debugger-3.2.1-1.0.0.zip > (mac & linux) > > > %USERPROFILE%\.vscode\extensions\asf.apache-daffodil-vscode-1.0.0\server\core\target\universal\daffodil-debugger-3.2.1-1.0.0.zip > (windows) > > > > > > On 2022/03/03 18:38:56 Mike Beckerle wrote: > > > 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 (avail on github). This is > a > > > completely self-contained schema of 4 files. No jars. > > > > > > The main DFDL schema project file fo > > > that is > src/main/resources/EDIFACT-SupplyChain-D03B/EDIFACT-SupplyChain-Messages-D.03B.xsd > > > The data file I chose was > > > > src/test/resources/EDIFACT-SupplyChain-D03B/TestData/INVOIC_D.03B_Interchange_with_UNA.txt > > > > > > Element breakpoints in that first schema file worked great. I was able > to > > > look at the infoset-diff view which was helpful and pretty cool. > > > > > > The problem is element breakpoints in other files of this same schema > can > > > be set but do not do anything. > > > > > > I think we should reopen issue 66, and that needs fixing for this > initial > > > release for include/import files that do not involve jars/classpath. > > > > > > My vote -1. > > > > > > Other minor issue also detected the vsix installation created directory > > > ~/.local/share/daffodil-dap/daffodil-debugger-3.1.0-1.0.0-SNAPSHOT > > > Should be daffodil 3.2.1 version and "SNAPSHOT" shouldn't be in the > name. > > > > > > > > > > > > > > > On Wed, Mar 2, 2022 at 7:26 PM Shane Dell <shanedell...@gmail.com> > wrote: > > > > > > > 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 > > > > 86DDE7B41291E380237934F007570D3ADC76D51B, corresponding > > > > to shaned...@apache.org, which is included in the KEYS file here: > > > > > > > > https://downloads.apache.org/daffodil/KEYS > > > > > > > > The release candidate has been tagged in git with 1.0.0-rc1. > > > > > > > > For reference, here is a list of all closed GitHub issues tagged with > > > > 1.0.0: > > > > > > > > > > > > > https://github.com/apache/daffodil-vscode/issues?q=is%3Aissue+is%3Aclosed+is%3A1.0.0 > > > > > > > > Please review and vote. The vote will be open for at least 72 hours > > > > (Sunday, 6 March 2022, 12 Noon EST). > > > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove (and reason why) > > > > > > > > Thank you, > > > > > > > > - Shane Dell > > > > > > > > > >
