-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
no main manifest attribute, in jetty-runner-9.2.19.v20160908.jar #920
Comments
Bizarre: when I build jetty-9.2.20-SNAPSHOT locally, the Main-Class property is clearly in the MANIFEST.MF file. However, if I download the latest jetty-9.2.20-SNAPSHOT from https://oss.sonatype.org/content/repositories/jetty-snapshots/org/eclipse/jetty/jetty-runner/9.2.20-SNAPSHOT/, it isn't there! Investigating. |
This is still a problem in jetty 9.2.21 release too. @olamy didn't you do some work on this? |
well I remember having a look at the build. |
@olamy ah, I seem to remember that too. Do you recall which branch the fix was put into? |
might be this one https://github.com/olamy/jetty.project/tree/bug/deploy_osgi_missing (not really sure) |
If you want to submit those 2 commits as a PR, they look good. I'll merge em. |
sure. I will test again the fix. |
well after having a look at jetty-runner I wonder if this really need to be OSGI. |
yeah, I don't see why jetty-runner should have anything to do with osgi |
Bugfix for #920 (disable bundle plugin)
PR #1370 applied |
This reverts commit b3a9543. The problem probably due to jetty/jetty.project#920 Change-Id: I20b2b1da1c7e1ab53247dc0793e2d4b13f0d16e6
Today I have used latest 9.2.* version - jetty-runner-9.2.19.v20160908.jar and I have got this error:
pene@petr-ThinkPad-T410:~/run$ sudo java -jar -Dabra.basicstorage.home=basicstorage jetty-runner-9.2.19.v20160908.jar --port 80 igate.war
[sudo] heslo pro pene:
no main manifest attribute, in jetty-runner-9.2.19.v20160908.jar
I have seen there is fix for version 9.3.*. Is it possible to merge the fix to version 9.2?
The text was updated successfully, but these errors were encountered: