On Fri, Nov 8, 2013 at 2:13 PM, Vít Ondruch notifications@github.comwrote:

well, the plugin does download the gem from a maven repository

This is the first step I don't understand. What is downloaded actually? If
that would be:

Download gem from rubygems.org

Download pom.xml from maven repository

That would sound acceptable.

both come from a maven repository

But you say "download gem from a maven repository". So the gems are
mirrored?

basically, actually when you trigger the download there will be a redirect
to the storage grom rubygems.org. but that is how the torquebox maven gem
repo works. there a nexus-plugin for ruby which offers also repo for gem
artifacts there the gem gets mirrored in the nexus server.

Are they modified? Are they converted to jars? Are they trusted?

not modified. not converted. just put along pom.xml in maven directory
layout. trusted - that is something.

would it help (in the long run) to use a 'ruby script' instead of the
gem-maven-plugin- or ? there is ruby gem which helps to convert a gemspec
into pom.xml - does that help ?

Since I am nor Java nor Maven expert, that would be definitely more
comprehensible.

well, there are two things:

maven downloads the gem from that gem maven repo - for that the plugin is
not needed, that is core maven.
the plugin installs the gem at the configured place

Still not sure why are the gems mavenized anyway.

well, let's say it is just convenient like maven caches the download in the
local repository, etc

For Fedora, we are definitely not going to download anything from any
maven repository out there, so I see it just as a complication. But I
understand that your build/release process is different, so I just like to
highlight Fedoras different POV and find solution which will work for both.

that is understood ;)

Uh oh!

Unbundle krypt libraries #1207

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions