Any important differences between the IKVM 8.15.0 preview using IKVM.Maven.Sdk 1.10.0 and the final 8.15.0 release using IKVM.Maven.Sdk 1.11.0? #705
Replies: 4 comments 4 replies
-
|
I have tried a different system but still get the errors (this time in English so hopefully clearer for most people reading here): |
Beta Was this translation helpful? Give feedback.
-
|
Nope. |
Beta Was this translation helpful? Give feedback.
-
|
I can say your project is configured very weirdly though. SaxonHE10Net31Samples has a PackageReference to the SaxonHE10Net31Api package. But the project is sitting right next to it. |
Beta Was this translation helpful? Give feedback.
-
|
The samples project is in there to later consume the Nuget package, you are right it is a bit odd but it makes it easier for consumers of the Api package to find a sample on how to use it in the same repo. For the IKVM 8.15.0 release with IKVM.Maven.Sdk 1.11.0 I have so far not produced an Api package and have not yet tried to run it. So as odd as it might appear, it is not part of the problem I have run into with my attempt to update the solution to use IKVM 8.15.0. I have tried it on two different machines with the same error popping up. Well, the whole project started with .NET Core 3.1, I sure thought there would be an open source SaxonCS HE from Saxonica within a .NET release or two later. Now we are with .NET 10. At least two comments from Michael Kay and O'Neil from Saxonica suggest next year we will see SaxonCS 13, and they said earlier that Saxon 13 will have a HE edition (not quite open source as they have an in house transpiler from Java to C# but want to only publish the created .NET software package(s) probably). Then my attempts to use IKVM to keep Saxon running with HE version under .NET are no longer needed, and will probably also no longer possible as they move to Java 17. Anyway, until then, and as .NET 10 is official now, I wanted a .NET 10 build of the Saxon HE 10.9 project. Worked out fine with the preview of IKVM 8.15 but now fails with the release. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have run into a strange problem, when the preview of IKVM 8.15.0 appeared I managed to update my .NET projects for Saxon HE 10.9 to .NET 10, all packages/projects could be built without problems.
Today I have moved to the final IKVM 8.15.0 release (that also involves an update to IKVM.Maven.Sdk 1.11.0) and two of my packages/projects don't build any more, with some error about a type or namespace in
net.sf.saxonnot being found.I have tried to clean and build the projects a few times, but always get the same error.
Then I saved the changes in a new branch and checked whether the old branch still worked, and indeed it does.
So does anyone know what changes between IKVM 8.15.0 preview (and IKVM.Maven.Sdk 1.10.0) and the final 8.15.0 release (and the update to IKVM.Maven.Sdk 1.11.0) could explain the problem?
The Gitub project is https://github.com/martin-honnen/SaxonHE10Net31/, the branch that uses the preview of IKVM 8.15.0 (and IKVM.Maven.Sdk 1.10.0) is https://github.com/martin-honnen/SaxonHE10Net31/tree/IKVM815NET10, the branch with the final release of IKVM 8.15.0 and with IKVM.Maven.Sdk 1.11.0 is https://github.com/martin-honnen/SaxonHE10Net31/tree/IKVM815MavenSdk110NET10.
I build using the VS 2026 command line tools under Windows 11 e.g. in the various project with
dotnet build --configuration Release. The projects SaxonHE10Net31 and SaxonHE10Net31Api build fine with both branches, but for the branch IKVM815MavenSdk110NET10 building SaxonHE10Net31Xslt and SaxonHE10Net31XQuery fails, errors are e.g.or
The net.sf.saxon.Transform and net.sf.saxon.Query are defined in Saxon HE 10.9 Java which is included in the project SaxonHE10Net31 via a MavenReference https://github.com/martin-honnen/SaxonHE10Net31/blob/IKVM815MavenSdk110NET10/SaxonHE10Net31/SaxonHE10Net31.msbuildproj#L31.
Any hints appreciated.
Beta Was this translation helpful? Give feedback.
All reactions