You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A conversation I had on Discord with @AliveDevil resulted in this.
IKVM.NET.Sdk should support the inclusion of .jar files along side it's existing support for .class and .java files. This will assist @AliveDevil with his project. But also, it's the right place to put it. The goal of IKVM.NET.Sdk is to be a .NET Project type, which produces exactly one output assembly (like every other .NET project type), and there's nothing wrong with it being able to source the input for that production from multiple different types of files. This can be used by users to convert existing JAR files to Assemblies for the purposes of export/redistribution. IkvmReference isn't appropriate for this, because it's geared towards consuming Java libraries for the purpose of using them in an existing project, not for exporting or publishing them.
The text was updated successfully, but these errors were encountered:
A conversation I had on Discord with @AliveDevil resulted in this.
IKVM.NET.Sdk should support the inclusion of .jar files along side it's existing support for .class and .java files. This will assist @AliveDevil with his project. But also, it's the right place to put it. The goal of IKVM.NET.Sdk is to be a .NET Project type, which produces exactly one output assembly (like every other .NET project type), and there's nothing wrong with it being able to source the input for that production from multiple different types of files. This can be used by users to convert existing JAR files to Assemblies for the purposes of export/redistribution. IkvmReference isn't appropriate for this, because it's geared towards consuming Java libraries for the purpose of using them in an existing project, not for exporting or publishing them.
The text was updated successfully, but these errors were encountered: