Skip to content

Proposal: NuGet Package(s)? #1084

Open
Open
@jonpryor

Description

@jonpryor

The problem(s):

  1. How do we ("reasonably") test generator changes against e.g. xamarin/AndroidX to ensure we don't break things?

  2. How do we ("reasonably") update the generator used by e.g. xamarin/AndroidX to fix bugs that are encountered there? (See also [generator] Fix NRE by cloning method when copying from base type to derived type. #1080)

    Currently the only way to update generator is to update the entire SDK packages used, the Xamarin.Android package and .NET Android package. This is time consuming and cumbersome.

A possible answer? NuGet Packages!

Proposal: begin creating and publishing Java.Interop.* NuGet package(s) which contain generator and related tools.

Open Questions:

  • Package name conventions; do we go with Java.Interop as a prefix? Xamarin.Java.Interop or Microsoft.Java.Interop? Other?
  • Should generator (and class-parse, and…) be in a global dotnet tool format? Would this need to be a separate pacakge-per-tool, or can multiple such tools be in a single package?
  • We have at least one request to publish the "standalone" builds ofJava.Interop.dll and Java.Runtime.Environment.dll in a NuGet package; see also c6c487b. I think this is a reasonable idea. These should not be included in the generator package.

Metadata

Metadata

Assignees

No one assigned

    Labels

    generatorIssues binding a Java library (generator, class-parse, etc.)proposalIssue raised for discussion, we do not even know if the change would be desirable yet

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions