Skip to content
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

Closed
petr-n opened this issue Sep 12, 2016 · 10 comments
Closed

no main manifest attribute, in jetty-runner-9.2.19.v20160908.jar #920

petr-n opened this issue Sep 12, 2016 · 10 comments
Assignees
Labels
Bug For general bugs on Jetty side
Milestone

Comments

@petr-n
Copy link

petr-n commented Sep 12, 2016

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?

@janbartel janbartel self-assigned this Sep 15, 2016
@joakime joakime added this to the 9.2.x milestone Nov 1, 2016
@joakime joakime added the Bug For general bugs on Jetty side label Nov 1, 2016
@janbartel
Copy link
Contributor

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.

@joakime
Copy link
Contributor

joakime commented Mar 1, 2017

This is still a problem in jetty 9.2.21 release too.

@olamy didn't you do some work on this?

@olamy
Copy link
Member

olamy commented Mar 2, 2017

well I remember having a look at the build.
But I didn't really fix it in any branch as 9.2.x is deprecated/obsolete.
let me know I can have a look for sure.

@joakime
Copy link
Contributor

joakime commented Mar 2, 2017

@olamy ah, I seem to remember that too. Do you recall which branch the fix was put into?

@olamy
Copy link
Member

olamy commented Mar 2, 2017

might be this one https://github.com/olamy/jetty.project/tree/bug/deploy_osgi_missing (not really sure)
Not sure but it was issue with bundle plugin executed in the wrong phase.

@joakime
Copy link
Contributor

joakime commented Mar 2, 2017

If you want to submit those 2 commits as a PR, they look good. I'll merge em.

@olamy
Copy link
Member

olamy commented Mar 2, 2017

sure. I will test again the fix.
I will probably focus only on jetty-runner.

@olamy
Copy link
Member

olamy commented Mar 2, 2017

well after having a look at jetty-runner I wonder if this really need to be OSGI.
As it's simply an uber jar so nothing really OSGI style.
WDYT?

@jmcc0nn3ll
Copy link
Contributor

yeah, I don't see why jetty-runner should have anything to do with osgi

janbartel added a commit that referenced this issue Mar 15, 2017
Bugfix for #920 (disable bundle plugin)
@janbartel
Copy link
Contributor

PR #1370 applied

wmfgerrit pushed a commit to wikimedia/wikidata-query-deploy that referenced this issue Nov 6, 2018
This reverts commit b3a9543.
The problem probably due to jetty/jetty.project#920

Change-Id: I20b2b1da1c7e1ab53247dc0793e2d4b13f0d16e6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side
Projects
None yet
Development

No branches or pull requests

5 participants