Maven Dependency is looking for LIRE files in local dir

[GoogleCodeExporter]

From an HowTo's comment:

When I add JFeaturelib as a Maven dependency in Netbeans (7.3), this happens: 
"Failed to read artifact descriptor for net.semanticmetadata:lire:jar:0.9.3: 
Could not transfer artifact net.semanticmetadata:lire:pom:0.9.3 from/to lib 
(file://${project.basedir}/lib): Repository path /lib does not exist, and 
cannot be created"

Is this some internal local dependency? I actually do have a "lib" folder, 
although it doesn't contain the lire pom/jar. I have lire available as a maven 
dependency, but JFeaturelib appears to be looking for it in a very specific 
place.

There should be a better solution for this.

Original issue reported on code.google.com by franz.graf on 2 May 2013 at 8:05

[GoogleCodeExporter]

As I do not know an official repo for Lire, I added it manually into the lib 
folder. Unfortunately this doesn't seem to work as expected.

Original comment by franz.graf on 2 May 2013 at 8:06

[GoogleCodeExporter]

Asked lire authors directly
https://groups.google.com/forum/?fromgroups=#!topic/lire-dev/-yP3SrNb1t4

Original comment by franz.graf on 2 May 2013 at 8:13

[GoogleCodeExporter]

First error I found was, that there are SNAPSHOT dependencies in the maven 
central jar. (guava-14-SNAPSHOT) which won't work. This is since version 1.3.x.

However I could not reproduce your error with Eclipse or maven commandline 
(using version 1.2.0). I will try it with Netbeans as soon as possible. 

In the meantime I would recommend to create a special Maven Build Descriptor 
[1] which is part of the Maven Assembly Plugin [2]. With this descriptor the 
lire and lux package should be included in the "normal" jar.

The other possible way would be to include the "jar-with-dependencies", where 
all libraries are packaged.

[1] 
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-
and-excluding-artifacts.html
[2] http://maven.apache.org/plugins/maven-assembly-plugin/

Original comment by nepomuk....@gmail.com on 2 May 2013 at 10:04

[GoogleCodeExporter]

Fixed the guava dependency in f78ecc688ec2 .

Let's wait if Mathias (Lire) want's to move to Maven. I'll keep the options 1,2 
in mind. Yet I am not sure if the problem will soon be solved anyways.

Original comment by franz.graf on 4 May 2013 at 10:05

[GoogleCodeExporter]

Hi guys,

Thanks for trying to solve this - I guess there's not much you can do if the 
Lire author has no plans to mavenise the project soon.
Until this happens (or someone makes the "jar-with-dependencies" include Lire 
too as per nepomuk's post), is there an easy workaround?
As of now, I can't use JFeaturelib at all with Maven :-/

Original comment by denpasho...@gmail.com on 29 May 2013 at 11:15

[GoogleCodeExporter]

Nevermind, I found a fix that seems to work for me.
First, I added Lire as a manually-installed dependency.
Then I added JFeaturelib 1.2.0 as a dependency, then edited 
~/.m2/repository/de/lmu/ifi/dbs/jfeaturelib/JFeatureLib/1.2.0/JFeatureLib-1.2.0.
pom and removed the "repositories" node (lines 99-113), which seems to cause 
maven to look for files in /lib - at least on this box running OS X.

Perhaps that node shouldn't be in the pom?

Original comment by denpasho...@gmail.com on 29 May 2013 at 4:03

[GoogleCodeExporter]

Removing the node might be an option. But still - one wouldn't be able to use 
the lib without manually installing lire in maven.

Another solution might be to include the lire code in JFeatureLib directly.
I'll try to evaluate if there's a maven way to do that automatically or - if 
nothing else works - possibly add the Lire code directly into the code base.

Original comment by franz.graf on 6 Jun 2013 at 6:52

[GoogleCodeExporter]

> But still - one wouldn't be able to use the lib without manually installing 
lire in maven.

Without removing that node myself, I wasn't able to use the lib with or without 
manually installing lire in maven!

Original comment by denpasho...@gmail.com on 6 Jun 2013 at 10:06

[GoogleCodeExporter]

I am currently uploading a 1.3.3-SNAPSHOT maven artifact that should also 
include LIRE in the JAR.
Does it work this way?

Original comment by franz.graf on 10 Jun 2013 at 7:21

[GoogleCodeExporter]

Hi Franz, where have you uploaded that snapshot? I can't find it on the central 
Maven repository.

Original comment by denpasho...@gmail.com on 18 Jun 2013 at 11:55

[GoogleCodeExporter]

Hi sorry it took me so long. I had severe problems w/ my internet.
I just uploaded v 1.3.3-RC1 to 
https://oss.sonatype.org/content/repositories/releases/de/lmu/ifi/dbs/jfeatureli
b/JFeatureLib/1.3.3-RC1/
Maybe the snapshot was already cleaned up by Sonatype.

Original comment by franz.graf on 23 Jun 2013 at 7:24

[GoogleCodeExporter]

should be fixed by v 1.4

Original comment by franz.graf on 15 Jul 2013 at 6:13

• Changed state: Done