Non-parseable POM #81
Comments
|
If I can make an un-educated guess, maven directly feeds on |
|
well the maven fails to install the extension which allows those ruby files as pom ;) in the output there is these lines: this file itself should have some info what went wrong with downloading the mavengem-wagon-0.2.1.pom does it gives you some hints ? |
|
Sorry for the late reply. Yes it does: Am I guessing correctly that the installer tries to source mavengem-wagon directly from maven rather than from my source specified in the Jarfile? I am sitting behind a corporate firewall, so such a request will never work for me. |
|
Btw, should I be using jar-dependencies instead? I'm a bit lost at what the differences are, which one is the way forward. |
|
@cburgmer jar-dependencies is the way forward unless you use warbler (or any other) which needs jbundler. jar-dependencies comes with jruby and jbundler uses jar-dependencies under the hood. mavengem-wagon is only the first of three such files which are needed to add the ruby extension to maven. there is corporate maven repo, I think the only way to go is to add a settings.xml file in your project pointing to that repo within an active profile. the source in Jarfile is too late as it needs the ruby maven extension already in place. |
|
Indeed a settings.xml in the project directory works. This works for me: <?xml version="1.0" encoding="UTF-8"?>
<settings xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns="http://maven.apache.org/SETTINGS/1.1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<profiles>
<profile>
<repositories>
<repository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>libs-release</name>
<url>http://my.intra.net/repository/libs-release</url>
</repository>
<repository>
<snapshots />
<id>snapshots</id>
<name>libs-snapshot</name>
<url>http://my.intra.net/repository/libs-snapshot</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>plugins-release</name>
<url>http://my.intra.net/repository/plugins-release</url>
</pluginRepository>
<pluginRepository>
<snapshots />
<id>snapshots</id>
<name>plugins-snapshot</name>
<url>http://my.intra.net/repository/plugins-snapshot</url>
</pluginRepository>
</pluginRepositories>
<id>myprofile</id>
</profile>
</profiles>
<activeProfiles>
<activeProfile>myprofile</activeProfile>
</activeProfiles>
</settings>I'm assuming this will also affect jar-dependencies. Can we document this behaviour somewhat, or make it easier to discover? |
|
yes, jar-dependencies will be the same. yes, need to add it - honestly I was not aware until your issue even though I use local proxy/mirror for maven. |
|
Great. Thanks a lot for your quick and precise help!
Will look at jar-dependencies now.
|
|
Am still having issue with the latest 0.9.3 version of the gem with the same Non-parseable POM Exception. Any suggestions please? |
|
@karthik-krishnan sorry for the delayed answer. the original issue was that not all artifacts used by maven are downloaded and then maven can not parse the pom.rb. post the output of |
|
@karthik-krishnan possibly related elastic/logstash#5325 (comment) |
|
I have a quite similar issue 'Non-parseable POM' with the latest Jbundler 0.9.3 version when running a project. Here is the output of Any idea on how to fix this? |
so basically this failed. do you have access to maven-central, i.e. not blocked by any corporate firewall, etc ? |
|
Thanks! I think it's corporate firewall problem as I tried with another computer outside company domain it could work. |
|
@TonyGan329 if you have a maven proxy/mirror then you can set ENV |
|
Hi! I am also having the same issue. I don't think its a networking issue, like the person above, since I was able to successfully Here's the output of |
|
@ecdemis123 from the logs I see a problem downloading one jar, please have a look into /home/vagrant/.m2/repository/org/torquebox/mojo/mavengem-wagon/0.2.1/mavengem-wagon-0.2.1.pom.lastUpdated which might gives you some clues. but without this file and its dependency jruby-core jar it will not work. really need to catch this case and produce a more useful error message |
|
Okay, here are the contents of that file. Can you give me any context on this? I am not familiar with java/maven development 😄 |
|
Ok I found a work around and I'll post my solution in case this helps someone else in the future. |
|
@ecdemis123 I did not know anything about the protocol version but this thread indicated a jdk7 problem: technomancy/leiningen#2364 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
jbundle installwithgem 'jbundler', '0.9.3'installed with the Jarfileyields the following output:
Rolling back to
gem 'jbundler', '0.5.4'works.Context:
Here's the full debug output:
Btw, 0.5.4 seems to be the latest version that works for us, here's a summary of went wrong for the latest minor versions in between:
gem 'jbundler', '0.7.4'gem 'jbundler', '0.6.4'The text was updated successfully, but these errors were encountered: