On 07/12/2013 12:52 AM, Orion Poplawski wrote:
I'm trying to fix up the jruby pom install, but not having much
luck.
It appears that the package just might not provide a proper pom for the
jruby.jar file. The closest is in maven/jruby/pom.xml, but I get:
+ python -m /usr/share/java-utils/maven_depmap
/export/home/orion/redhat/BUILDROOT/jruby-1.7.2-3.fc19.x86_64/usr/share/maven-fragments/jruby
/export/home/orion/redhat/BUILDROOT/jruby-1.7.2-3.fc19.x86_64/usr/share/maven-poms/JPP-jruby.pom
''
Traceback (most recent call last):
File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/usr/share/java-utils/maven_depmap.py", line 301, in <module>
fragment = parse_pom(pom_path, jar_path)
File "/usr/share/java-utils/maven_depmap.py", line 142, in parse_pom
raise PackagingTypeMissingFile(pom_path)
__main__.PackagingTypeMissingFile: Packaging type is not 'pom' and no
artifact path has been provided for pom
/export/home/orion/redhat/BUILDROOT/jruby-1.7.2-3.fc19.x86_64/usr/share/maven-poms/JPP-jruby.pom
Any suggestions? Thanks.
(I'm looking at red5 and it is looking for a org.jruby:jruby artifact.)
That POM has packaging type 'jar'. In this case you need to specify
path to the JAR file, but from the trace it looks like you passed an
empty string.
Showing the exact macro call as well as location of installed POM and
JAR files would help me debug the problem.
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk