Skip to content

Git: Add missing package import org.ietf.jgss to JGIT packages - #9755

Open
matthiasblaesing wants to merge 1 commit into
apache:deliveryfrom
matthiasblaesing:jgit_import_jgss
Open

matthiasblaesing wants to merge 1 commit into
apache:deliveryfrom
matthiasblaesing:jgit_import_jgss

Conversation

@matthiasblaesing

@matthiasblaesing matthiasblaesing commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Both org.eclipse.jgit and org.eclipse.jgit.ssh.apache are missing imports for org.ietf.jgss causing ClassNotFoundExceptions when Negotiate/Kerberos Authentication is invoked.

Closes: #9751

@matthiasblaesing matthiasblaesing added this to the NB32 milestone Oct 27, 2026
@matthiasblaesing matthiasblaesing added git [ci] enable versioning job ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) labels Oct 27, 2026
The NetBeans module org.eclipse.jgit.ssh.apache is just a repackaging
of the original bundle, with org.ietf.jgss added to the Import Package
list.
-->

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is not a sustainable solution. I tried to get a patch into jgit and it is still bitrotting. Maybe that changed and they are more open, but my gut feeling is, that more project have broken imports and thus will break. So for a hotfix I would go with #9756 if that works.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... not a sustainable solution...

  • patching upstream projects in NetBeans repository isn't sustainable solution
  • submitting patches to upstream projects is (in my opinion) the only sustainable solution
  • please submit the patch to jgit and reference it here

...more project have broken imports...

  • that's possible, but unless we know about them it is just a guess
  • once we find such a project, we should (again) submit patch upstream (in my opinion)

hotfix I would go with #9756 if that works.

  • that's probably safest bet for NetBeans 32 - feel free to do it
  • for master I'd rather stick to Felix/OSGi spec and fix broken OSGi module imports one by one
  • with a bit of luck we'll fix them all by NetBeans 33

@neilcsmith-net neilcsmith-net Oct 28, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for master I'd rather stick to Felix/OSGi spec and fix broken OSGi module imports one by one

That is not how this works! The commit in #9756 will sync to master from delivery. Nothing ever lands only in the release.

I agree with @matthiasblaesing that patching here is not a sustainable nor desirable option, from a technical and provenance point of view. So, as and until any built-in dependencies don't require it, we're stuck with that.

And -1 to this.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I know that delivery is synced both ways (the release, as well as master)

patching here is not a sustainable

  • Exactly!
  • Hence I want us to (try to) solve the issue upstream.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment seemed to suggest not merging to master. Sorry if I read that wrong.

We all want upstream fixed! But @matthiasblaesing has looked into this issue the most, and happy to leave it to his call on the best approach.

If everything is otherwise equal, I do prefer a time-limited opening of the configuration over patching. I do prefer keeping binary identity of third-party deps, and I'm unsure if we've definitely covered every base on the imports? It's obvious upstream isn't automating and testing for this.

@neilcsmith-net neilcsmith-net added the do not merge Don't merge this PR, it is not ready or just demonstration purposes. label Oct 28, 2026
Both org.eclipse.jgit and org.eclipse.jgit.ssh.apache are missing
imports for org.ietf.jgss causing ClassNotFoundExceptions when
Negotiate/Kerberos Authentication is invoked.

Closes: apache#9751
@matthiasblaesing matthiasblaesing changed the title Git: Add missing package org.ietf.jgss to Import-Package for org.eclipse.jgit.ssh.apache Git: Add missing package import org.ietf.jgss to JGIT package Oct 28, 2026
@matthiasblaesing matthiasblaesing changed the title Git: Add missing package import org.ietf.jgss to JGIT package Git: Add missing package import org.ietf.jgss to JGIT packages Oct 28, 2026
@matthiasblaesing

Copy link
Copy Markdown
Contributor Author

JGit Changerequest: https://gerrithub.io/c/eclipse-jgit/jgit/+/1257440

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) do not merge Don't merge this PR, it is not ready or just demonstration purposes. git [ci] enable versioning job

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Git: Connection can't be established behind proxy with Kerberos authentication

3 participants