-
-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception in JarEditor maybe in combination with sub-bundles #5951
Comments
@pkriens I tried adding info on how to reproduce. Maybe something is going on here https://github.com/bndtools/bnd/blob/master/bndtools.jareditor/src/bndtools/jareditor/internal/TemporaryFile.java#L44 |
Herculean work man! I am going to take this and keep it in mind. The fix seems ok. I vaguely recall I also had a problem in this area and did a fix but either age, alzheimer, or korsakov makes me unable to recall. I've been working on some stuff might be in there, will take a look. Thanks. |
Today I was experimenting with sub-bundles (as here) and I got this often.
this was another related stacktrace:
Reproducer Repo
I created a small reproducer repo at https://github.com/chrisrueger/bndtools-jareditorbug
It's a bnd workspace.
Steps to reproduce
I could not exactly reproduce the initally report stack trace but I think a related behavior:
Notice there are 2 .bnd files.
Sub-Bundles are enabled.
My expectation is that an
my.bundle1.api.jar
is to be built/generated/my.bundle1.api.jar
in the JAR Editor and switch to the Print tab (this switch seems to be important)May this already triggers the exception report initally. But for me it just happened the first time.
You should see something like this:
This stacktrace and the stacktrace in the issue description share the same line:
at bndtools.jareditor.internal.TemporaryFile.lambda$tempFolder$0(TemporaryFile.java:44)
To reproduce it over and over again do the following:
/generated/my.bundle1.api.jar
/generated/my.bundle1.api.jar
and open the Print tab.Boom. Error again.
Error does not happen when you skip 5. Close the Jar Editor
Repeat 5-8 and you always get the error.
The text was updated successfully, but these errors were encountered: