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.

Sign up for GitHub

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

Jump to bottom

Remove jpm from setup instructions or pressure to fix #28

Closed
jjohnson opened this issue Jul 9, 2016 · 6 comments
Closed

Remove jpm from setup instructions or pressure to fix #28

jjohnson opened this issue Jul 9, 2016 · 6 comments

Comments

@jjohnson
Copy link

jjohnson commented Jul 9, 2016 

curl http://www.jpm4j.org/install/script > installjpm.sh
sudo sh installjpm.sh
sudo jpm -te install com.codacy:codacy-coverage-reporter:assembly

Using settings file: ~/.jpm/settings.json
# default
# home=/var/jpm, bin=/usr/local/bin
# home=/var/jpm, bin=/usr/local/bin
# install com.codacy:codacy-coverage-reporter:assembly
# coordinate com.codacy:codacy-coverage-reporter:assembly
# -> {jsonrpc:"2.0",method:"getRevisionByCoordinate",params:["com.codacy:codacy-coverage-reporter:assembly"],id:1468032023592}
# Sentx 
# Error 
# <- http://repo.jpm4j.org/jsonrpc/2.0/jpm
# ERROR: [URLClient.send] http://repo.jpm4j.org/jsonrpc/2.0/jpm
java.lang.Exception: http://repo.jpm4j.org/jsonrpc/2.0/jpm
    at aQute.rest.urlclient.URLClient.send(URLClient.java:162)
    at aQute.rest.urlclient.URLClient.put(URLClient.java:179)
    at aQute.jsonrpc.proxy.JSONRPCProxy.invokeSync(JSONRPCProxy.java:91)
    at aQute.jsonrpc.proxy.JSONRPCProxy.invoke(JSONRPCProxy.java:63)
    at com.sun.proxy.$Proxy5.getRevisionByCoordinate(Unknown Source)
    at aQute.jpm.lib.JustAnotherPackageManager.getCandidateAsync(JustAnotherPackageManager.java:942)
    at aQute.jpm.lib.JustAnotherPackageManager.getCandidate(JustAnotherPackageManager.java:903)
    at aQute.jpm.main.Main._install(Main.java:472)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at aQute.lib.getopt.CommandLine.execute(CommandLine.java:149)
    at aQute.jpm.main.Main._jpm(Main.java:366)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at aQute.lib.getopt.CommandLine.execute(CommandLine.java:149)
    at aQute.jpm.main.Main.run(Main.java:797)
    at aQute.jpm.main.Main.main(Main.java:118)
Caused by: java.lang.Exception: Failed request 405:HTTP method PUT is not supported by this URL <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 405 </title>
</head>
<body>
<h2>HTTP ERROR: 405</h2>
<p>Problem accessing /jsonrpc/2.0/jpm. Reason:
<pre>    HTTP method PUT is not supported by this URL</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>
    at aQute.rest.urlclient.URLClient.send(URLClient.java:130)
    ... 20 more
Error
  0. [URLClient.send] http://repo.jpm4j.org/jsonrpc/2.0/jpm

You could also just navigate to http://jpm4j.org/ or http://repo.jpm4j.org and see the 405

Also doubt your other product will build if you commit there, https://github.com/codacy/codacy-api-java/blob/fix/docs/circle.yml
@jjohnson jjohnson mentioned this issue Jul 9, 2016
Closed
@pedrorijo91
Copy link
Contributor

Hey @jjohnson

Sorry for taking some time to answer to your issue.

Is it still happening? We have some internal projects that are using this plugin and they didn't report any problem as far as I know. It seems more a rare problem that affected JPM servers

@halkeye
Copy link

halkeye commented Aug 21, 2016

as of early august, the https certificates are expired.

Can this be distributed another way?

@pedrorijo91
Copy link
Contributor

pedrorijo91 commented Aug 21, 2016 •
edited

Hey @halkeye,

Have you tried to build from source as a temporary solution?

Just warned jpm4j maintainers about the expired certificate, and we will think about a solution as soon as we know something from their side

@halkeye
Copy link

halkeye commented Aug 21, 2016

not yet, i'm still trying to figure out how I want to do all this from a CI platform, so just poking around at options for now.

As with #22, I might look into learning how to make maven plugins.

@pedrorijo91
Copy link
Contributor

if you decide to go for a maven plugin, let us know. We will gladly help you in everything we can @halkeye :)

@pedrorijo91
Copy link
Contributor

closing as duplicated from #22

ljmf00 pushed a commit to ljmf00/codacy-coverage-reporter that referenced this issue Aug 28, 2019
@rtfpessoa
Merge pull request codacy#28 from codacy/fix-publish
4eedb3e 
fix: Duplicate developpers tag when publishing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@halkeye @jjohnson @pedrorijo91